Warp wrote:
> 4) gdb will report the exact line where it crashed. The most useful thing
>    to do now is to write "bt" (shorthand for "backtrace")
> 
> 5) If needed, you can print the values of variables in scope with the
>    "print" command.

Does it work for C++ also the same way? Or just C?  As in, does the -g give 
it enough information to unmunge the global names and walk the stack in 
spite of inline functions and such?  Just curious.

-- 
   Darren New, San Diego CA, USA (PST)
   "Ouch ouch ouch!"
   "What's wrong? Noodles too hot?"
   "No, I have Chopstick Tunnel Syndrome."

Post a reply to this message