public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17016] New: XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld rtld_map_complete
Date: Wed, 04 Jun 2014 12:45:00 -0000	[thread overview]
Message-ID: <bug-17016-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 17016
           Summary: XFAIL: gdb.threads/dlopen-libpthread.exp: info probes
                    all rtld rtld_map_complete
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: palves at redhat dot com

I'm seeing this new XFAIL/UNTESTED on Fedora 20, compared to a test run I had
done a month ago, on Fedora 17:

 -PASS: gdb.threads/dlopen-libpthread.exp: info probes all rtld
rtld_map_complete
 -PASS: gdb.threads/dlopen-libpthread.exp: libpthread.so not found
 -PASS: gdb.threads/dlopen-libpthread.exp: set variable
filename="dlopen-libpthread.so"
 -PASS: gdb.threads/dlopen-libpthread.exp: continue to breakpoint: notify
 -PASS: gdb.threads/dlopen-libpthread.exp: libpthread.so found
 +XFAIL: gdb.threads/dlopen-libpthread.exp: info probes all rtld
rtld_map_complete
 +UNTESTED: gdb.threads/dlopen-libpthread.exp: dlopen-libpthread.exp

I'm surprised this XFAILs on Fedora 20 while it passed on F17.  The .exp file
doesn't include any hint on why this could be normal.  If this is really
expected, and I'm missing something on my system, it'd be good if the test had
a comment to the effect.

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


             reply	other threads:[~2014-06-04 12:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04 12:45 palves at redhat dot com [this message]
2014-09-24 18:04 ` [Bug gdb/17016] " sergiodj at redhat dot com
2014-09-24 18:04 ` sergiodj at redhat dot com
2022-12-24  7:45 ` vries at gcc dot gnu.org
2022-12-24 11:19 ` [Bug testsuite/17016] " vries at gcc dot gnu.org
2022-12-24 11:32 ` vries at gcc dot gnu.org
2022-12-30 15:53 ` cvs-commit at gcc dot gnu.org
2022-12-30 15:55 ` vries at gcc dot gnu.org

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-17016-4717@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).