28 Jun, 2006, Sanami wrote in the 1st comment:
Votes: 0
I have a problem with my EOS2 (diku/merc/envy/eos) code crashing when a mprog or sedit is used wrong. When I go into gdb and try to find the problem all I get is something that looks like this:

Reading symbols from shared object read from target memory…(no debugging symbols found)…done.
Using host libthread_db library "/lib/libthread_db.so.1".
Loaded system supplied DSO at 0x694000
Core was generated by `../bin/abyss 8456'.
Program terminated with signal 11, Segmentation fault.
#0 0x0071c907 in ?? ()
(gdb) bt
#0 0x0071c907 in ?? ()
#1 0x00000009 in ?? ()
#2 0x00000025 in ?? ()
#3 0x3b305b1b in ?? ()
#4 0x37333b31 in ?? ()
#5 0xbfea006d in ?? ()
#6 0x0809e191 in ?? ()
#7 0x0937d400 in ?? ()
#8 0xbfea194c in ?? ()
#9 0x007e2158 in ?? ()
#10 0x0937a288 in ?? ()
#11 0x0000000d in ?? ()
#12 0xb7cf61b1 in ?? ()
#13 0xbfea1928 in ?? ()
#14 0x08094ca8 in ?? ()
#15 0x00000000 in ?? ()

Any suggestions on how to get it to something I could possible understand?
28 Jun, 2006, Guest wrote in the 2nd comment:
Votes: 0
Did you compile your code using the -g flag in the Makefile? This tells it to include debugging information. -g is normal, -g2 adds some detail, and -g3 adds even more.
28 Jun, 2006, Sanami wrote in the 3rd comment:
Votes: 0
DEBUG = -g3
28 Jun, 2006, Midboss wrote in the 4th comment:
Votes: 0
Have you considered using Valgrind instead? I find it tends to be a lot more helpful than GDB in pretty much every case. If your server already has it installed, just go to the area directory and do valgrind –tool=corecheck ../src/<exe file> <port>. If you don't have Valgrind installed, I'd strongly recommend talking to your server admin and getting it put in, as it really is a useful tool.
28 Jun, 2006, Halcyon wrote in the 5th comment:
Votes: 0
Very real possibility that he simply isn't calling GDB in the right place. Not absolutely sure how that works, to tell the truth, but my executable is always in the same place as the source, so maybe that's it.
29 Jun, 2006, Zeno wrote in the 6th comment:
Votes: 0
Try attaching gdb to the process, if you're trying to debug a crash.