Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "John R. Moore" <jmoore@cygnus.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix for gdb-gnats bug #14
Date: Fri, 16 Feb 2001 16:44:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0102161638530.1722-100000@bosch.cygnus.com> (raw)
In-Reply-To: <200102170027.QAA01551@bosch.cygnus.com>

On Fri, 16 Feb 2001, Michael Elizabeth Chastain wrote:

> I proofread this patch plus I tested on a Solaris 2.6 native with gcc
> 2.9-gnupro-99r1.  It works for me.
> 
> I recommend that the maintainers approve the patch as submitted.
> 
> But I have more comments ...
> 
> I note that the test has two branches: an hpux branch and a non-hpux
> branch.  This is strange, because the underlying feature is not
> target specific.
> 
> The hpux branch contains the correct expectatation: it expects the "step"
> commands not to run.  I checked this by reading the test carefully and
> also by examining test results:
> 
>   /tantor/build/gnupro-00r1/hppa1.1-hp-hpux10.20/tests/hppa1.1-hp-hpux10.20/010214/gdb/testsuite/gdb.log 
>   /tantor/build/gnupro-00r1/sparc-sun-solaris2.6/tests/sparc-sun-solaris2.6/010204/gdb/testsuite/gdb.log 
> 
> So:
> 
>   . gdb always behaves as documented in the manual
>   . the hpux version of the test is correct.
>     gdb behaves as documented, and the test PASSes.
>   . the non-hpux version of the test is incorrect.
>     gdb behaves as documented, but the test FAILs.
>   . your patch actually makes the non-hpux test the same as the hpux test
> 
> If you care to do more work, you could remove the hpux test, kill the
> non-hpux expression completely, and use the hpux expression on all
> platforms.
> 
> It's up to the maintainers (Stan Shebs and Fernando Nasser) whether
> to accept the patch or remand it for more work.  I recommend accepting it
> and then doing more work as a second patch.
> 
> Michael Elizabeth Chastain

I (of course) noted the same and wondered why the hpux might be
different, but didn't give it a second thought, thinking that there
always could be an exception (and besides, I didn't have an hpux
to try it out on).

I see no big deal (do more work) to eliminate the hpux exception.
It might be that somebody somewhere fixed this once on an hpux,
but didn't bother to fix any other os?  The more work would simply
involve removing the "if hpux" block of script.

John


       reply	other threads:[~2001-02-16 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200102170027.QAA01551@bosch.cygnus.com>
2001-02-16 16:44 ` John R. Moore [this message]
2001-02-18 15:57 Michael Elizabeth Chastain
  -- strict thread matches above, loose matches on Subject: below --
2001-02-16 17:54 Michael Elizabeth Chastain
2001-02-16 17:19 Michael Elizabeth Chastain
2001-02-16 17:36 ` Michael Snyder
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=Pine.LNX.4.21.0102161638530.1722-100000@bosch.cygnus.com \
    --to=jmoore@cygnus.com \
    --cc=chastain@cygnus.com \
    --cc=gdb-patches@sources.redhat.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