The example further below my attempt to use gdb on a generated core file following a segmentation error (my gdb experience is mostly on a running process) [xxx, yyy, and zzz are substitutes for real paths/files]. I just want a backtrace to see the line where the crash occurred, but the reading of symbols seems to be too much to handle. Is there a way to skip the reading of sets of symbols? Thanks in advance. Jim Jones Icon Labs #gdb myprog myprog.core Core was generated by `myprog'. Program terminated with signal 6, Abort trap. Reading symbols from xxx.so...done. Reading symbols from yyy.so.1.2...done. Reading symbols from /usr/lib/libkvm.so.5.0...done. Reading symbols from /usr/lib/libcrypt.so.0.0...done. Reading symbols from zzz.so.1.0... gdb: virtual memory exhausted: can't allocate 4795804 bytes. # [note: I am assuming that gdb should have remained open for issuing backtrace commands and such]
