From: Michael Snyder <msnyder@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: jmoore@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix for gdb-gnats bug #14
Date: Fri, 16 Feb 2001 17:36:00 -0000 [thread overview]
Message-ID: <3A8DD5B1.D7CFA9D2@cygnus.com> (raw)
In-Reply-To: <200102170119.RAA01860@bosch.cygnus.com>
Michael Elizabeth Chastain wrote:
>
> Hi John,
>
> As I understand it, HP and Cygnus did a lot of gdb development on a branch
> and then contributed big blocks of it back to the FSF code base. I wasn't
> around at the time, so maybe somebody who was can comment on the history.
Close enough. HP did the work separately, Cygnus attempted to merge it.
> This looks like someone was merging an HP chunk and saw that it was
> different from the baseline. So they took the HP version and wrapped
> it in a test for 'istarget "hppa*-hp-hpux*"' test.
Probably right.
> But the hpux version is right (for all platforms) and the non-hpux
> version is wrong (for all platforms).
Correct. In fact, this test has always been wrong, and AFAIK,
it could never ever ever have passed. I don't understand how
it has existed as such.
> > (and besides, I didn't have an hpux to try it out on).
>
> I don't have access to an hpux at the moment either. :( But I do have
> recent log files from a Red Hat project. Here are excerpts:
>
> # hppa1.1-hp-hpux10.20 native
> (gdb) PASS: gdb.base/commands.exp: commands in infrun_breakpoint_command_test #2
> continue^M
> Continuing.^M
> ^M
> Breakpoint 7, factorial (value=5) at ***/run.c:77^M
> 77 if (value > 1) {^M
> 78 value *= factorial (value - 1);^M
> (gdb) PASS: gdb.base/commands.exp: continue in infrun_breakpoint_command_test
>
> # solaris 2.6 native
> (gdb) PASS: gdb.base/commands.exp: commands in infrun_breakpoint_command_test #2
> continue^M
> Continuing.^M
> ^M
> Breakpoint 7, factorial (value=5) at ***/run.c:77^M
> 77 if (value > 1) {^M
> 78 value *= factorial (value - 1);^M
> (gdb) FAIL: gdb.base/commands.exp: continue in infrun_breakpoint_command_test
>
> > I see no big deal (do more work) to eliminate the hpux exception.
>
> That would be great. If my archeological theory is right, you would be
> resolving a merge item that never got completely merged.
I don't understand why it isn't a FAIL on RH7. The output is
identical to the failing output on Solaris.
next prev parent reply other threads:[~2001-02-16 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 17:19 Michael Elizabeth Chastain
2001-02-16 17:36 ` Michael Snyder [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-18 15:57 Michael Elizabeth Chastain
2001-02-16 17:54 Michael Elizabeth Chastain
[not found] <200102170027.QAA01551@bosch.cygnus.com>
2001-02-16 16:44 ` John R. Moore
2001-02-16 13:44 Michael Elizabeth Chastain
2001-02-16 13:56 ` John R. Moore
2001-02-16 10:04 John R. Moore
2001-02-16 14:40 ` John R. Moore
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=3A8DD5B1.D7CFA9D2@cygnus.com \
--to=msnyder@cygnus.com \
--cc=chastain@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jmoore@cygnus.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