From: Martin Simmons <qqxnjvamvxwx@dyxyl.com>
To: Roger Phillips <heidegg@hotmail.com>
Cc: gdb@sourceware.org
Subject: Re: Missing memory mappings
Date: Wed, 28 Feb 2024 12:37:11 +0000 [thread overview]
Message-ID: <jer0gw3gug.fsf@localhost> (raw)
In-Reply-To: <PH7PR22MB4048891E1AF54B952003B802AA502@PH7PR22MB4048.namprd22.prod.outlook.com> (message from Roger Phillips via Gdb on Tue, 20 Feb 2024 12:27:57 +0000)
>>>>> On Tue, 20 Feb 2024 12:27:57 +0000, Roger Phillips via Gdb said:
>
> I'm doing post-mortem coredump analysis for multithreaded C++
> applications on x64 Linux. Occasionally I get coredumps where some
> threads (not the crashing thread) has instruction pointers that look
> valid but cannot be matched to a memory region provided by info proc
> mappings. So my assumption is that these libs have been unloaded
> between the signal and the creation of the coredump and I wonder in
> which library load scenarios this could happen.
Maybe the vdso section, which is not dumped?
> This might not be a gdb problem but a coredump problem but I don't
> know where else to find the expertise.
You could see what 'objdump -x' says about the coredump's sections.
__Martin
prev parent reply other threads:[~2024-02-28 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 12:27 Roger Phillips via Gdb
2024-02-28 12:37 ` Martin Simmons [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=jer0gw3gug.fsf@localhost \
--to=qqxnjvamvxwx@dyxyl.com \
--cc=gdb@sourceware.org \
--cc=heidegg@hotmail.com \
/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