Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Philippe Blain via Gdb <gdb@sourceware.org>
Cc: Philippe Blain <levraiphilippeblain@gmail.com>
Subject: Re: Recovering a core dump deleted while debugging
Date: Fri, 28 Aug 2026 13:23:05 -0600	[thread overview]
Message-ID: <87v78u82xy.fsf@tromey.com> (raw)
In-Reply-To: <D9652366-DEAD-429F-97DE-0E581749D1E3@gmail.com> (Philippe Blain via Gdb's message of "Wed, 26 Aug 2026 07:53:16 -0400")

> I’m debugging a core dump in GDB and some other process deleted the
> directory where the core dump was. Is there anyway to recover it?

Probably not.

> I tried 'lsof -p $pid' and looking in /proc/$pid/fd/ but the core dump
> does not appear there. I’m guessing GDB closes the file after it loads
> everything into memory ?

BFD sometimes closes file descriptors, so you might have run into this.
gdb can also cause BFD to do this, though exactly when is kind of opaque
to the user.

Checking /proc is pretty much the only thing I would have suggested.

Tom

  reply	other threads:[~2026-08-28 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 11:53 Philippe Blain via Gdb
2026-08-28 19:23 ` Tom Tromey [this message]
2026-09-01 11:03   ` Philippe Blain via Gdb

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=87v78u82xy.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb@sourceware.org \
    --cc=levraiphilippeblain@gmail.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