Bug#443822: I've found a fix (for: hex-a-hop: Got bt from a segfault :D)

[Gerfried Fuchs]

* Jens Seidel <jensseidel at users.sf.net> [2008-11-22 11:28:12 CET]:
> On Fri, Nov 21, 2008 at 01:03:21PM +0100, Gerfried Fuchs wrote:
> >  Hmm, have you checked? The segfault still happens to me regularly, and
> > strace isn't really helpful here, even gdb is acting strange to me:
> 
> Sorry, I do not remember it well. At least it seems that I cared about the
> case numStages==0 (according to the bug log).

 Hmm, alright.

> Clearly this package needs more care which requires more time. At least I
> will try to increase both soon but I cannot promise it.

 It seems so. The game is too much fun to let it go, though. :/

> > gdb> bt
> > #0  0x0fbd68dc in ?? () from /lib/libc.so.6
> > #1  0x0fbd5a20 in memmove () from /lib/libc.so.6
> > #2  0x00000000 in ?? ()
> > 
> >  As I'm not too familiar with gdb I really would appreciate some help to
> > debug this further and offer more helpful informations...
> 
> This happens on PowerPC, right?

 Exactly.

> I have access to i386, mips, mipsel only. I'm sure valgrind would help
> (valgrind hex-a-hop) but this doesn't support exotic architectures and
> I could not reproduce this bug with it in the past.

 valgrind does run it, but extremely slow. And I mean slow. Given that
the bug doesn't happen always at the same stage and can't be narrowed
down enough this is really painful ...

> Maybe a memory checker such as efence would help as well, not sure.

 How would I incorporate it?
Rhonda