From: "Taras D" <taras.di@gmail.com>
To: gdb@sourceware.org
Subject: stack trace and breaking before crash
Date: Mon, 10 Mar 2008 15:45:00 -0000 [thread overview]
Message-ID: <4024fa2d0803100824t788d284cq438043063335c750@mail.gmail.com> (raw)
In-Reply-To: <4024fa2d0803100747g289cf2abl248dbc80b007356a@mail.gmail.com>
Hi everyone,
I have two questions:
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?
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.
I'm running gdb on cygwin.
Thanks
Taras
next parent reply other threads:[~2008-03-10 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4024fa2d0803100747g289cf2abl248dbc80b007356a@mail.gmail.com>
2008-03-10 15:45 ` Taras D [this message]
2008-03-10 15:54 ` Andreas Schwab
2008-03-10 16:02 ` Brian Dessent
2008-03-10 16:36 ` Brian Dessent
2008-03-11 15:25 ` Taras D
2008-03-11 17:49 ` Brian Dessent
2008-03-11 17:53 ` Daniel Jacobowitz
2008-03-11 21:03 ` Brian Dessent
2008-03-12 12:34 ` Taras D
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4024fa2d0803100824t788d284cq438043063335c750@mail.gmail.com \
--to=taras.di@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox