This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: stack trace and breaking before crash
- From: Brian Dessent <brian at dessent dot net>
- To: Taras D <taras dot di at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Mon, 10 Mar 2008 08:53:52 -0700
- Subject: Re: stack trace and breaking before crash
- References: <4024fa2d0803100747g289cf2abl248dbc80b007356a@mail.gmail.com> <4024fa2d0803100824t788d284cq438043063335c750@mail.gmail.com>
- Reply-to: gdb at sourceware dot org
Taras D wrote:
> 1) A program that crashes is writing a stack trace. However, the stack
> trace is in heaxadecimal. Is there anyway of replacing the hexadecimal
> numbers with symbols?
Set error_start to dumper to get a real core dump instead of the stack
trace file. Then load the core into gdb.
> 2) Is it possible to get gdb to break before the program crashes? In
> VS 2003, the program breaks execution before the crash allowing
> inspection of the stack/variables/etc. The exception I'm getting is:
> Exception: STATUS_ACCESS_VIOLATION at eip=610AE0E9. I've tried typing
> in bt after the crash occurs but the output doesn't seem to be a stack
> trace of the running program.
Set error_start to gdb and you will be taken to the point of the
exception when it occurs.
Brian