From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: chastain@cygnus.com, shebs@apple.com
Cc: ac131313@cygnus.com, cagney@cygnus.com,
gdb-patches@sourceware.cygnus.com, kettenis@wins.uva.nl,
msnyder@cygnus.com
Subject: Re: [RFA] Testsuite addition for x86 linux GDB and SIGALRM fix
Date: Thu, 28 Jun 2001 13:02:00 -0000 [thread overview]
Message-ID: <200106282002.NAA29458@stanley.cygnus.com> (raw)
Ah, I have an example in the existing test suite.
gdb.base/funcargs.c has several functions with one-line bodies:
#ifdef PROTOTYPES
void call5a (struct stag st)
#else
call5a (st)
struct stag st;
#endif
{st.s1 = 5;}
In some configurations, this causes problems because gcc optimizes away
the stabn for the end of the prologue. gdb needs that stabn; without
that stabn, it ultimately comes up with a bogus place to breakpoint and
thus prints incorrect values of the "st" argument.
I've seen this happen on native i686-pc-cygwin and native i686-pc-linux
with a gcc v2 compiler. I haven't seen it happen with a gcc v3 compiler.
I haven't filed a bug report yet.
The bug depends on the fact that the whole function body is one line.
The Gnu Coding Standard prohibits this:
http://www.gnu.org/prep/standards_22.html#SEC22
MichaelC
next reply other threads:[~2001-06-28 13:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 13:02 Michael Elizabeth Chastain [this message]
[not found] <200106281927.MAA29407@stanley.cygnus.com>
2001-06-28 12:41 ` Stan Shebs
[not found] <200005192321.e4JNLEv13368@delius.kettenis.local>
2001-06-27 22:22 ` Andrew Cagney
2001-06-28 10:54 ` Michael Snyder
2001-07-09 14:21 ` Fernando Nasser
2001-07-09 14:34 ` Daniel Jacobowitz
[not found] ` <3B4A2C7C.85C688C4@cygnus.com>
2001-07-09 15:17 ` Daniel Jacobowitz
2001-07-09 15:28 ` Fernando Nasser
2001-07-25 16:11 ` Michael Snyder
2001-07-25 16:45 ` Fernando Nasser
2001-07-25 18:48 ` Andrew Cagney
2001-07-26 7:14 ` Fernando Nasser
2001-07-26 7:44 ` Eli Zaretskii
2001-07-26 7:51 ` Eli Zaretskii
2001-07-26 8:18 ` Eli Zaretskii
2001-07-26 8:48 ` Fernando Nasser
2001-07-26 8:56 ` Eli Zaretskii
2001-07-26 10:21 ` Fernando Nasser
2001-07-26 10:38 ` Fernando Nasser
2001-07-26 10:06 ` Andrew Cagney
2001-07-26 10:24 ` Fernando Nasser
2001-07-26 10:45 ` Andrew Cagney
2001-07-26 10:54 ` Fernando Nasser
2001-07-26 6:10 ` Michael Snyder
2001-07-26 7:14 ` Fernando Nasser
2001-07-26 7:45 ` Michael Snyder
2001-07-26 7:51 ` Fernando Nasser
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=200106282002.NAA29458@stanley.cygnus.com \
--to=chastain@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=cagney@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=kettenis@wins.uva.nl \
--cc=msnyder@cygnus.com \
--cc=shebs@apple.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