On Sat, 2009-02-07 at 14:25 -0500, Matthew Talbert wrote:
> > Oh, sorry. I assume you have verified that you don't have any heap
> > corruption by running the code under valgrind on Linux? Other than
> > that I really can't give any specific advice. Perhaps ask somebody
> > else to read the code ca
> Oh, sorry. I assume you have verified that you don't have any heap
> corruption by running the code under valgrind on Linux? Other than
> that I really can't give any specific advice. Perhaps ask somebody
> else to read the code carefully. If the problem did not occur at some
> earlier stage, the
> Not trying to be offensive, but if I could reproduce this every time,
> I wouldn't be asking for debugging suggestions.
Oh, sorry. I assume you have verified that you don't have any heap
corruption by running the code under valgrind on Linux? Other than
that I really can't give any specific advi
On Thu, Feb 5, 2009 at 4:38 AM, Tor Lillqvist wrote:
>
> > I would appreciate any suggestions as to how to debug this further.
>
> Write a minimal sample program that exhibits the problem, file a bug,
> and attach the sample program (as a single source file in C; no
> binaries, not zip archives, n
> I would appreciate any suggestions as to how to debug this further.
Write a minimal sample program that exhibits the problem, file a bug,
and attach the sample program (as a single source file in C; no
binaries, not zip archives, no makefiles) to the bug.
-tml
__
