[GEM-dev] Problem with GEM/PMPD

[Mathieu Bouchard]

On Sun, 6 Mar 2011, Jack wrote:

> Program received signal SIGSEGV, Segmentation fault.
> 0x002f182b in ?? () from /lib/libc.so.6
> (gdb) bt
> #0  0x002f182b in ?? () from /lib/libc.so.6
> #1  0x002f2ced in ?? () from /lib/libc.so.6
> #2  0x002f698a in ?? () from /lib/libc.so.6
> #3  0x002f6f53 in realloc () from /lib/libc.so.6
> #4  0x080af7d6 in resizebytes ()
> #5  0x085b0b50 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> (gdb)

Try it with valgrind instead of gdb.

Both are very useful debuggers, but they don't help in the same 
circumstances as each other.

In case of corrupt stack, corrupt heap (malloc assertion failed) and 
unexplainable crashes in non-buggy code, valgrind finds the cause, not the 
consequence.

  _______________________________________________________________________
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC