public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Roger Phillips <heidegg@hotmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Missing memory mappings
Date: Tue, 20 Feb 2024 12:27:57 +0000	[thread overview]
Message-ID: <PH7PR22MB4048891E1AF54B952003B802AA502@PH7PR22MB4048.namprd22.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

Greetings,

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.

This might not be a gdb problem but a coredump problem but I don't know where else to find the expertise.

Regards.

             reply	other threads:[~2024-02-20 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 12:27 Roger Phillips [this message]
2024-02-28 12:37 ` Martin Simmons

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=PH7PR22MB4048891E1AF54B952003B802AA502@PH7PR22MB4048.namprd22.prod.outlook.com \
    --to=heidegg@hotmail.com \
    --cc=gdb@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).