12 Aug
2013
12 Aug
'13
6:30 a.m.
On 08/08/2013 03:56 AM, Steve Glass wrote:
Ok, so its telling you that there is a bad pointer
being passed to
free. Things you can do: * Set "ulimit -c unlimited" in the shell
before running the program. That way you get a "core" file when the
program crashes and can run the debugger on it to find out why. *
Run valgrind on the executable. When the program finishes it will
produce a summary of all memory errors. Hope that helps. Stevie
op25 finally died again. all i got out of gdb was:
Core was generated by `/usr/bin/python -u
/home/matt/OP25_GRC/op25_grc.py'.
Program terminated with signal 11, Segmentation fault.
#0 0x081000bb in ?? ()
(gdb) i stack
#0 0x081000bb in ?? ()
#1 0x00000000 in ?? ()
(gdb)
valgrind printed a bunch of complaints upon starting the grc but i was
unable to get anything out of that shell after the crash other than
the same old backtrace and memory map. there was no command prompt so
something had to still be running; perhaps valgrind?
any ideas about the above gdb output? or how to get more out of
valgrind?
Thanks a bunch