From: Chris Sutcliffe <ir0nh34d@gmail.com>
To: gdb@sourceware.org
Subject: Re: gdb built from gcc 4.6.1 has some crash problem
Date: Tue, 11 Oct 2011 22:51:00 -0000 [thread overview]
Message-ID: <CAGHJv4dyfGmyo4UGCP2itjP0uKz4ECMMc-899JQch4G73c7F1g@mail.gmail.com> (raw)
In-Reply-To: <4E94471F.3010609@gmail.com>
On 11 October 2011 09:39, asmwarrior wrote:
> Does this issue happened in Linux also?
FWIW, I've confirmed this behaviour using mingw.org's gcc 4.6.1 to
compile 7.3.1. I then compiled 7.3.1 using the gcc 4.6.1 that shipped
with Arch Linux and was not able to re-create the issue (I experienced
the 'good' behaviour). So this issue seems specific to the mingw
target for gcc 4.6.x.
In terms of next steps, is this something that should be brought up on
the gcc mailing list?
Thank you,
Chris
--
Chris Sutcliffe
http://emergedesktop.org
http://www.google.com/profiles/ir0nh34d
next prev parent reply other threads:[~2011-10-11 22:51 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 [this message]
[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
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=CAGHJv4dyfGmyo4UGCP2itjP0uKz4ECMMc-899JQch4G73c7F1g@mail.gmail.com \
--to=ir0nh34d@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