Re: problem with "where" command in gdb v3.1.2

Thread View: gnu.gdb.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Ron Guilmette Fri, 16 Jun 1989 20:15

#45

Author: Ron Guilmette
Date: Fri, 16 Jun 1989 20:15

13 lines
1020 bytes

I have often seen the problem described by Amante with GDB.

A simple solution is to set a breakpoint on the library
function named "abort" before you start executing the program
being debugged.  Then, when you hit that breakpoint, the
"where" command should still work.  By the time you make it
into abort (or kill) however, the "where" command does in
fact give you only incomplete information.

// Ron Guilmette  -  MCC  -  Experimental Systems Kit Project
// 3500 West Balcones Center Drive,  Austin, TX  78759  -  (512)338-3740
// ARPA: rfg@mcc.com
// UUCP: {rutgers,uunet,gatech,ames,pyramid}!cs.utexas.edu!pp!rfg

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads