public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "amerey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31031] New: gcore misses non-contiguous file mappings Date: Fri, 03 Nov 2023 19:39:53 +0000 [thread overview] Message-ID: <bug-31031-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31031 Bug ID: 31031 Summary: gcore misses non-contiguous file mappings Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: amerey at redhat dot com Target Milestone: --- Created attachment 15209 --> https://sourceware.org/bugzilla/attachment.cgi?id=15209&action=edit copy of /proc/PID/maps While looking into https://sourceware.org/bugzilla/show_bug.cgi?id=30975 I noticed that gcore produces corefiles with missing file mappings in NT_FILE if the segments for some shared library are not all contiguous. To reproduce this on RHEL 7.9, run python and let it idle while waiting for user input. Generate a corefile for this process with gcore, then kill the process with `kill -11` to generate a corefile through systemd (systemd coredumps must be enabled). I've attached 2 corefiles that were generated with the above procedure. The non-contiguously loaded shared library in question is ld-2.17.so. systemd.core NT_FILE contains: [...] 7f432a373000-7f432a3b1000 0017f000 253952 /usr/lib64/libpython2.7.so.1.0 7f432a3c0000-7f432a3e2000 00000000 139264 /usr/lib64/ld-2.17.so 7f432a5d8000-7f432a5df000 00000000 28672 /usr/lib64/gconv/gconv-modules.cache 7f432a5e1000-7f432a5e2000 00021000 4096 /usr/lib64/ld-2.17.so 7f432a5e2000-7f432a5e3000 00022000 4096 /usr/lib64/ld-2.17.so while gcore.core NT_FILE contains: [...] 7f432a373000-7f432a3b1000 0017f000 253952 /usr/lib64/libpython2.7.so.1.0 7f432a5e1000-7f432a5e2000 00021000 4096 /usr/lib64/ld-2.17.so 7f432a5e2000-7f432a5e3000 00022000 4096 /usr/lib64/ld-2.17.so An ld segment and a gconv segment are missing from gcore.core but present in systemd.core. I've also attached a copy of the python process' /proc/PID/maps file, which agrees with systemd.core. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2023-11-03 19:39 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-03 19:39 amerey at redhat dot com [this message] 2023-11-03 19:40 ` [Bug gdb/31031] " amerey at redhat dot com 2023-11-03 19:40 ` amerey at redhat 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-31031-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: linkBe 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).