This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: About the "info locals" command of gdb and python pretty printer

From: Tom Tromey <tromey at redhat dot com>
To: asmwarrior <asmwarrior at gmail dot com>
Cc: gdb at sourceware dot org
Date: Mon, 21 Jun 2010 20:18:03 -0600
Subject: Re: About the "info locals" command of gdb and python pretty printer
References: <4C1DDBB0.9010202@gmail.com> <m3tyowgnd2.fsf@fleche.redhat.com> <4C2003E8.3000407@gmail.com>
Reply-to: tromey at redhat dot com

>>>>> ">" == Asm gmail <asmwarrior@gmail.com> writes:

>> I'm not sure how to get a "stack track" when gdb crashed. Do I need to
>> run GDB under GDB. So, the debuggee GDB get crashed, the debugger GDB
>> can generate some stack trace inforamtion?

Yes.  Or at least, try that, and if it does not work we may need to look
into alternatives.

Tom

References:
- About the "info locals" command of gdb and python pretty printer
  - From: asmwarrior
- Re: About the "info locals" command of gdb and python pretty printer
  - From: Tom Tromey
- Re: About the "info locals" command of gdb and python pretty printer
  - From: asmwarrior

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]