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 corefiles/27689] New: FAIL: gdb.base/gcore-tls-pie.exp: x/i $pc
Date: Fri, 02 Apr 2021 15:36:33 +0000	[thread overview]
Message-ID: <bug-27689-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 27689
           Summary: FAIL: gdb.base/gcore-tls-pie.exp: x/i $pc
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: corefiles
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

On openSUSE tumbleweed, I see:
...
FAIL: gdb.base/gcore-tls-pie.exp: x/i $pc
FAIL: gdb.base/gcore-tls-pie.exp: unstripped + core ok
...

In more detail:
...
(gdb) file
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/gcore-tls-pie/gcore-tls-pie^M
Reading symbols from
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/gcore-tls-pie/gcore-tls-pie...^M
(gdb) core
/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/gcore-tls-pie/gcore-tls-pie.gcore^M
warning: core file may not match specified executable file.^M
[New LWP 7361]^M
Core was generated by
`/data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/gcore-tls-pie/gcor'.^M
Program terminated with signal SIGTRAP, Trace/breakpoint trap.^M
#0  0x00005555555546dd in ?? ()^M
(gdb) PASS: gdb.base/gcore-tls-pie.exp: re-load generated corefile
x/i $pc^M
=> 0x5555555546dd:      mov    $0x0,%eax^M
(gdb) FAIL: gdb.base/gcore-tls-pie.exp: x/i $pc
...

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

             reply	other threads:[~2021-04-02 15:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-02 15:36 vries at gcc dot gnu.org [this message]
2021-04-05 14:17 ` [Bug corefiles/27689] " vries at gcc dot gnu.org
2021-04-05 14:21 ` vries at gcc dot gnu.org
2021-04-05 14:27 ` vries at gcc dot gnu.org
2021-04-05 18:40 ` vries at gcc dot gnu.org
2021-04-07 12:56 ` vries at gcc dot gnu.org
2021-04-07 13:07 ` vries at gcc dot gnu.org
2021-04-07 13:22 ` vries at gcc dot gnu.org
2021-04-07 13:39 ` vries at gcc dot gnu.org
2021-04-09  9:31 ` vries at gcc dot gnu.org
2024-02-16  2:54 ` amodra at gmail dot com

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-27689-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).