From: Asmwarrior <asmwarrior@gmail.com>
To: xunxun <xunxun1982@gmail.com>
Cc: Chris Sutcliffe <ir0nh34d@gmail.com>,
gdb@sourceware.org,
MinGW Users List <mingw-users@lists.sourceforge.net>
Subject: Re: gdb built from gcc 4.6.1 has some crash problem
Date: Fri, 21 Oct 2011 03:04:00 -0000 [thread overview]
Message-ID: <4EA0BF9F.7070203@gmail.com> (raw)
In-Reply-To: <4E94E6CE.5060603@gmail.com>
Hi, all. Just for a record.
This reason that gdb crash on WinXP build from gcc 4.6.x can be found here:
http://lists.gnu.org/archive/html/qemu-devel/2011-10/msg02462.html
When building gdb with "-omit-frame-pointer" disabled, gdb works well.
Also, Kai Tietz supplies a patch to solve this problem. (I'm not sure
how the patch works, does it just disable the -omit-frame-pointer on
I386 for mingw?)
asmwarrior
ollydbg from codeblocks' forum
next prev parent reply other threads:[~2011-10-21 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 13:38 asmwarrior
2011-10-11 22:51 ` Chris Sutcliffe
[not found] ` <CA+BR0wynvgwW3btKZ+ftjjJ63htVHeScG97c3ovxNgpGrGvmOw@mail.gmail.com>
2011-10-12 0:42 ` Chris Sutcliffe
2011-10-12 1:01 ` xunxun
2011-10-21 3:04 ` Asmwarrior [this message]
2011-10-21 9:03 ` xunxun
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=4EA0BF9F.7070203@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=ir0nh34d@gmail.com \
--cc=mingw-users@lists.sourceforge.net \
--cc=xunxun1982@gmail.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