From: asmwarrior <asmwarrior@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] avoid the crash of gdb+pretty printer on initialized local variables
Date: Tue, 06 Dec 2011 10:34:00 -0000 [thread overview]
Message-ID: <4EDDAD62.9000103@gmail.com> (raw)
In-Reply-To: <m31usipubp.fsf@fleche.redhat.com>
On 2011-12-6 5:44, Tom Tromey wrote:
>>>>>> ">" == ext asmwarrior <asmwarrior@gmail.com> writes:
>
> Tom> I forget, something to do with not using the right gcc flag?
>
>>> My app was build with -O0 and -g, no extra flag is used.
>
> I mean a missing flag when building gdb. I vaguely recall a need for
> -fno-omit-frame-pointer, and that without this, gdb exceptions cause
> crashes.
>
> Tom
Hi, Tom, thanks.
Yes, gdb build under mingw should have -fno-omit-frame-pointer flag, otherwise, it will crash.
I forget to mention that My gdb was build with -O0 and -g, so I think no optimization was used in building gdb.
The problem is that gdb still crash when it try to pretty-print the uninitialized local variables.
asmwarrior
ollydbg from codeblocks' forum
next prev parent reply other threads:[~2011-12-06 5:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4ED379D8.4060808@gmail.com>
2011-12-02 4:32 ` asmwarrior
2011-12-02 16:51 ` Tom Tromey
2011-12-04 1:41 ` asmwarrior
[not found] ` <CAF4KFGqyz0WMWWJt9x1HZpO+urMo9jJLyudcRrHxUTqJf8mvqA@mail.gmail.com>
[not found] ` <CAF4KFGp2cDOzKdV62MfX0vpHUAxj1D2W0W3cBZnZpYHPYxZEuA@mail.gmail.com>
2011-12-05 10:13 ` Fwd: " Martin Runge
2011-12-05 12:48 ` André Pönitz
2011-12-20 14:38 ` Tom Tromey
2011-12-05 21:51 ` Tom Tromey
2011-12-06 10:34 ` asmwarrior [this message]
2011-12-06 15:41 ` Tom Tromey
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=4EDDAD62.9000103@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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