public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29850] [gdb, powerpc64le] FAIL: gdb.base/longjmp.exp: next over longjmp(1)
Date: Wed, 07 Dec 2022 08:33:20 +0000	[thread overview]
Message-ID: <bug-29850-4717-HEzy1Ldtca@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29850-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29850

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> (In reply to Tom de Vries from comment #1)
> > By inverting the branches:
> > ...
> > diff --git a/gdb/testsuite/gdb.base/longjmp.c
> > b/gdb/testsuite/gdb.base/longjmp.c
> > index 4139e49e6f1..ce6990ca99a 100644
> > --- a/gdb/testsuite/gdb.base/longjmp.c
> > +++ b/gdb/testsuite/gdb.base/longjmp.c
> > @@ -46,14 +46,14 @@ main ()
> >    volatile int i = 0;
> >  
> >    /* Pattern 1 - simple longjmp.  */
> > -  if (setjmp (env) == 0) /* patt1 */
> > +  if (setjmp (env) != 0) /* patt1 */
> >      {
> > -      longjmps++;
> > -      longjmp (env, 1);
> > +      resumes++;
> >      }
> >    else
> >      {
> > -      resumes++;
> > +      longjmps++;
> > +      longjmp (env, 1);
> >      }
> >  
> >    i = 1; /* miss_step_1 */
> > ...
> > we can avoid getting lucky on x86_64, and get the same result as for
> > powerpc64le.
> 
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;
> h=6e41445bb006f3afc784862f8eb1bf0f2691a94a

And now that that's fixed, x86_64 fails the same as powerpc64le, so marking
this a dup of PR26967.

*** This bug has been marked as a duplicate of bug 26967 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-12-07  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-05  9:02 [Bug gdb/29850] New: " vries at gcc dot gnu.org
2022-12-05 10:00 ` [Bug gdb/29850] " vries at gcc dot gnu.org
2022-12-05 10:03 ` vries at gcc dot gnu.org
2022-12-06 11:04 ` vries at gcc dot gnu.org
2022-12-07  8:33 ` vries at gcc dot gnu.org [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=bug-29850-4717-HEzy1Ldtca@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).