From: Tom Tromey <tromey@redhat.com>
To: Steve Ellcey <sellcey@mips.com>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
Pedro Alves <palves@redhat.com>,
<gdb-patches@sourceware.org>
Subject: Re: [PATCH] Avoid producing broken non-native core files
Date: Tue, 29 Oct 2013 17:38:00 -0000 [thread overview]
Message-ID: <87a9hs7z9v.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1383066110.2558.177.camel@ubuntu-sellcey> (Steve Ellcey's message of "Tue, 29 Oct 2013 10:01:50 -0700")
Steve> I do not get this error when using a newer GCC (like 4.4.3 or above). I
Steve> can work around it by setting siginfo_size to 0 when it is declared. I
Steve> don't know if there is a minimum GCC version required for building gdb
Steve> but my build with GCC 4.1.2 used to work. Do you think initializing
Steve> siginfo_size is reasonable to allow us to use older GCC's to build gdb?
FWIW, it's routine to commit changes like that in response to any
complaint.
Tom
prev parent reply other threads:[~2013-10-29 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 14:21 Maciej W. Rozycki
2013-10-16 15:22 ` Pedro Alves
2013-10-16 20:09 ` Maciej W. Rozycki
2013-10-18 15:12 ` Pedro Alves
2013-10-23 22:03 ` Maciej W. Rozycki
2013-10-24 14:32 ` Pedro Alves
2013-10-29 17:02 ` Steve Ellcey
2013-10-29 17:20 ` Maciej W. Rozycki
2013-10-29 17:28 ` Steve Ellcey
2013-10-29 17:38 ` Tom Tromey [this message]
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=87a9hs7z9v.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@codesourcery.com \
--cc=palves@redhat.com \
--cc=sellcey@mips.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