Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: gdb-patches@sources.redhat.com, Andrew Cagney <cagney@cygnus.com>,
	Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [PATCH] Fix xfail Sparc pattern
Date: Thu, 18 Apr 2002 07:48:00 -0000	[thread overview]
Message-ID: <3CBEDBEC.30BE86F8@redhat.com> (raw)
In-Reply-To: <200204171955.MAA09313@nuts.ninka.net>

"David S. Miller" wrote:
> 
> The xfail here applies to all Sparc platforms, not just sparc-*.
                 ^^^^^^^
> 

David,

You mean _does not_ apply.  The code is actually clearing the 
xfail setting for all architectures.

But before doing this, lets ask some questions areound (see below).



The way this is set up it will normally XFAIL unless one explicitly
unmark it.  A maintenance nightmare.

The comments say that the problem is:

        # The problem is that GDB confuses stepping through the call
        # dummy with hitting the breakpoint at the end of the call
dummy.
        # Will be fixed once all architectures define
        # CALL_DUMMY_BREAKPOINT_OFFSET.

Some architectures (listed in the clear_xfail commands) already define
it.
I suspect that many others may do it as well and noone ever unmarked
the xfail for this test.

Also, HP seems to define CALL_DUMMY_HAS_COMPLETED that also makes this
test
pass.  I wonder if this is some HP equivalent to the above.

The comments also say that this will work, regardless of the macro, for
the targets that:

        # This doesn't occur if the call dummy starts with a call,
        # because we are out of the dummy by the first time the inferior
        # stops.

and also for:

	# It works with the generic inferior function calling code too.

So, here is a question for Andrew:  what is the current status on
CALL_DUMMY_BREAKPOINT_OFFSET (and CALL_DUMMY_HAS_COMPLETED)?

I wonder if we should activate this test and see where it fails and
start marking as XFAILS (KFAILS actually) and entering a bug report 
when we see the regressions.

Regards to all.
Fernando



> 2002-04-17  David S. Miller  <davem@redhat.com>
> 
>         * gdb.base/watchpoint.exp: Fix sparc xfail to be sparc*-*-*
> 
> --- ./testsuite/gdb.base/watchpoint.exp.~1~     Tue Apr 16 10:56:47 2002
> +++ ./testsuite/gdb.base/watchpoint.exp Tue Apr 16 10:58:53 2002
> @@ -390,7 +390,7 @@ proc test_stepping {} {
>         # The following architectures define CALL_DUMMY_BREAKPOINT_OFFSET.
>         clear_xfail "alpha-*-*"
>         clear_xfail "mips*-*-*"
> -       clear_xfail "sparc-*-*"
> +       clear_xfail "sparc*-*-*"
>         clear_xfail "hppa*-*-*bsd*"
>         # It works with the generic inferior function calling code too.
>         clear_xfail "mn10200*-*-*"

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-04-18 14:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 12:57 David S. Miller
2002-04-18  7:48 ` Fernando Nasser [this message]
2002-04-18  9:06 Michael Elizabeth Chastain
2002-04-18  9:21 ` Andrew Cagney
2002-04-18 15:04   ` David S. Miller
2002-04-18 15:29     ` Andrew Cagney
2002-04-18 15:37       ` David S. Miller
2002-04-18 16:25         ` Andrew Cagney

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=3CBEDBEC.30BE86F8@redhat.com \
    --to=fnasser@redhat.com \
    --cc=cagney@cygnus.com \
    --cc=davem@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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