public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/31684] New: [gdb/testsuite] FAIL: gdb.base/corefile.exp: core-file warning-free
@ 2024-04-29 12:03 vries at gcc dot gnu.org
  2024-05-10  9:46 ` [Bug testsuite/31684] " vries at gcc dot gnu.org
  2024-05-10  9:48 ` vries at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2024-04-29 12:03 UTC (permalink / raw)
  To: gdb-prs

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

            Bug ID: 31684
           Summary: [gdb/testsuite] FAIL: gdb.base/corefile.exp: core-file
                    warning-free
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: testsuite
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With a tumbleweed container on a fedora asahi 39 system, I'm running into:
...
(gdb) core-file
/data/vries/gdb/build/gdb/testsuite/outputs/gdb.base/corefile/corefile.core^M
warning: Can't open file / (deleted) during file-backed mapping note
processing^M
[New LWP 1061096]^M
[Thread debugging using libthread_db enabled]^M
Using host libthread_db library "/lib64/libthread_db.so.1".^M
Core was generated by
`/data/vries/gdb/build/gdb/testsuite/outputs/gdb.base/corefile/corefile'.^M
Program terminated with signal SIGABRT, Aborted.^M
#0  0x0000ffff11e8d470 in __pthread_kill_implementation () from
/lib64/libc.so.6^M
(gdb) FAIL: gdb.base/corefile.exp: core-file warning-free
...

This doesn't seem to be something specific to gdb.

Using eu-readelf -n outputs/gdb.base/corefile/corefile.core we get:
...
  CORE                1001  FILE
    16 files:
      00400000-00404000 00000000 16384              
/data/vries/gdb/build/gdb/testsuite/outputs/gdb.base/corefile/corefile
      0041c000-00420000 0000c000 16384              
/data/vries/gdb/build/gdb/testsuite/outputs/gdb.base/corefile/corefile
      00420000-00424000 00010000 16384              
/data/vries/gdb/build/gdb/testsuite/outputs/gdb.base/corefile/corefile
      ffff11e00000-ffff11fa4000 00000000 1720320     /usr/lib64/libc.so.6
      ffff11fa4000-ffff11fbc000 001a4000 98304       /usr/lib64/libc.so.6
      ffff11fbc000-ffff11fc0000 001ac000 16384       /usr/lib64/libc.so.6
      ffff11fc0000-ffff11fc4000 001b0000 16384       /usr/lib64/libc.so.6
      ffff11fe0000-ffff12068000 00000000 557056      /usr/lib64/libm.so.6
      ffff12068000-ffff1207c000 00088000 81920       /usr/lib64/libm.so.6
      ffff1207c000-ffff12080000 0008c000 16384       /usr/lib64/libm.so.6
      ffff12080000-ffff12084000 00090000 16384       /usr/lib64/libm.so.6
      ffff12088000-ffff120b0000 00000000 163840      / (deleted)
      ffff120b0000-ffff120b4000 00000000 16384      
/data/vries/gdb/build/gdb/testsuite/outputs/gdb.base/corefile/coredir.1061040/coremmap.data
      ffff120b4000-ffff120b8000 00000000 16384      
/data/vries/gdb/build/gdb/testsuite/outputs/gdb.base/corefile/coredir.1061040/coremmap.data
      ffff120c4000-ffff120c8000 0002c000 16384       / (deleted)
      ffff120c8000-ffff120cc000 00030000 16384       / (deleted)
 ...

By running the exec under a debugger and doing "info proc mappings", it becomes
clear that the three "/ (deleted)" entries are for
/usr/lib/ld-linux-aarch64.so.1.

I don't see gdb doing something wrong (perhaps a kernel or podman problem?), so
tentatively classifying this as a testsuite problem.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug testsuite/31684] [gdb/testsuite] FAIL: gdb.base/corefile.exp: core-file warning-free
  2024-04-29 12:03 [Bug testsuite/31684] New: [gdb/testsuite] FAIL: gdb.base/corefile.exp: core-file warning-free vries at gcc dot gnu.org
@ 2024-05-10  9:46 ` vries at gcc dot gnu.org
  2024-05-10  9:48 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2024-05-10  9:46 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> With a tumbleweed container on a fedora asahi 39 system, I'm running into:

Likewise, a tumbleweed container on a leap 15.5 x86_64 system.

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug testsuite/31684] [gdb/testsuite] FAIL: gdb.base/corefile.exp: core-file warning-free
  2024-04-29 12:03 [Bug testsuite/31684] New: [gdb/testsuite] FAIL: gdb.base/corefile.exp: core-file warning-free vries at gcc dot gnu.org
  2024-05-10  9:46 ` [Bug testsuite/31684] " vries at gcc dot gnu.org
@ 2024-05-10  9:48 ` vries at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: vries at gcc dot gnu.org @ 2024-05-10  9:48 UTC (permalink / raw)
  To: gdb-prs

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> (In reply to Tom de Vries from comment #0)
> > With a tumbleweed container on a fedora asahi 39 system, I'm running into:
> 
> Likewise, a tumbleweed container on a leap 15.5 x86_64 system.

Likewise for test-case gdb.mi/mi-corefile.exp:
...
FAIL: gdb.mi/mi-corefile.exp: -target-select core $corefile (unexpected output)
...

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-05-10  9:48 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-04-29 12:03 [Bug testsuite/31684] New: [gdb/testsuite] FAIL: gdb.base/corefile.exp: core-file warning-free vries at gcc dot gnu.org
2024-05-10  9:46 ` [Bug testsuite/31684] " vries at gcc dot gnu.org
2024-05-10  9:48 ` vries at gcc dot gnu.org

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