On 12/2/05, David Carr <[EMAIL PROTECTED]> wrote: > I ran gschem in gdb this time and here's what I have so far:
FWIW, this is where core files can actually come in handy (post-mortem debugging). Sorry to bore you if you're already familiar with this. Instead of re-running the code in gdb, just set the maximum core file size to something other than 0 (in Bourne shell variants: "ulimit -c unlimited", or some large number in KB), and run the program unitl it crashes. Then, list the core file after the executable name when you invoke gdb. You should be able to do backtraces, potentially saving yourself some time in recreating the scenario that led up to the crash. -- - Charles Lepple
