From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id /kRUCCuxlmqmhxoAWB0awg (envelope-from ) for ; Tue, 01 Sep 2026 07:04:11 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=XkI7hysN; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 005531E09B; Tue, 01 Sep 2026 07:04:10 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-5.4 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED autolearn=ham autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [IPv6:2620:52:6:3111::32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 4A6641E09B for ; Tue, 01 Sep 2026 07:04:09 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 471624BA23E9 for ; Tue, 1 Sep 2026 11:04:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 471624BA23E9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1788260647; bh=8ijzPCKDFU1ejjq/7Uw5yJhHUCiABXNs6RW6YLjsNX8=; h=Subject:Date:References:Cc:In-Reply-To:To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=XkI7hysNk4yOHeajbSZeKSnKhzQyUkewrR7pcAbUXfv0wNsLNY8JInABDvd8mstlQ FfJ1e7LEWDHd6sWki8R5fET8tXddN0mk6hOJbfLwOf3B90FfZ6bD1eGMMi1ZGSdITa 3t9hyN35Oko0Ye3mrLKT9MGK987kapbA8TNrMRTg= Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) by sourceware.org (Postfix) with ESMTPS id 0CA914BA2E17 for ; Tue, 1 Sep 2026 11:03:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0CA914BA2E17 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 0CA914BA2E17 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1788260612; cv=none; b=oF3YDc/tgJLEK2f1fNA9D3x09jRXa6o26CgUcUYIFLgghguYmqC399GCm9dPgT2HC4oFohgYsluwXGbTxdkJItPRVn6TX4pQTulFU2r7NpadO716WtcOUC6x7W3VQfBNgQ2ZnLqjOUXIiBiZ9LCK6rdLa6xXN2ed/Z8VuuTheps= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1788260612; c=relaxed/simple; bh=8ijzPCKDFU1ejjq/7Uw5yJhHUCiABXNs6RW6YLjsNX8=; h=DKIM-Signature:From:Mime-Version:Subject:Date:Message-Id:To; b=T0IRUcROp5KxbfqGPvG7Jt3KzJ5YeYzR4QWOoEKqXxd0mJJswvtsMU9hgWWLDJ2g/b6/foQyFxbiMOboRSJ5eMwqL+JSWPhB3jLEJoGXbfABrwX/78vs4p0UIBZ7xzE66QMqyX28AnZfj27YU/MC19oEZLsQ0LEAEOsjCvFeFi4= ARC-Authentication-Results: i=1; sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20251104 header.b=psp7JcL2 DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CA914BA2E17 Received: by mail-qv1-xf29.google.com with SMTP id 6a1803df08f44-90d7fa95a58so27031326d6.1 for ; Tue, 01 Sep 2026 04:03:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1788260611; x=1788865411; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:content-type:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=8ijzPCKDFU1ejjq/7Uw5yJhHUCiABXNs6RW6YLjsNX8=; b=AMyZ4OKgDKtR/2dWV4no1vcGCbiwhaPXQJgTL7S1nV+dr2adQFU+UIXYCtIPgAJuEx SckI1oUYzd4t5bqg70FLTDH7qoEMlElUth4tcz+v/hNZFq+xvQOmgbvvzMYbb73864SC 7TdwRas5rphSkpLpUc6VtDN0gHLHEoqzWaDO3ObwlvpdEy9pAgFxJu609Jkc3t7x6k6f GPmnegmRZk78FW3b37WVhCOx/j2DgKG3/rtD87dGuOIGsDlTQ5xsBnYKgzXbmQXsGrdg wR3VtJcOK1CP01KD3CvjKYGZaFdh/vyf5oLk+shNf3yujoQjuTpqR47ajFM4xtuwgci1 9XbQ== X-Gm-Message-State: AFuF++mtvLW2lca9VqAzYt1SR0+yvI2a9BZOoPjjifASyga0cCZzLiWh Fe/fEKmiDKIQ161035OLKxedf4mCe27tGq+hB87mzWdKN3z7qOAg2hKHnE2Fgw== X-Gm-Gg: AYBFou3DCklOPAybTxMjvQcKsqbCOAyS9/qv5Tpe2HobszGVCigX4t5YzWkwd+jWaSx OmVIibhRL1FJfiI4tPCzcfWy1aE0CdCwx8uAtsSLc/kHvr9GUjmSu5MhCH88rN/TEe+bOz5bjQf uBaSGnHjUYxGOChtn8jC4HXJFtJZ/kD6tQ97vtq1j34J6oMaMmYP5ES1zff/wg8uR+llJUN44cj CWVOKGE9DinLaywOT7nOpDJDd0TQv4xFlvP/CmDEd5NS0v9f7BLGjA0wa0uuTq2eqyUv6mTYJGQ A4Y1BdruJPxiGOZUGPa2w5s5UL6n2xET6XrHi+f3ByZ0m9aJU22UEWuP8IID9rcxE8sQ4lQuiSi 6nFwT9dEACTICpCN49Ka7gdYQj+YD6W27ZmfuDOXs8txx/TmOv5kmJlpj2sVxV4IZ9mZ8Fz9Dbx qwjI08syV6iEueaRkZ87Gk6ma4huuKffEH1KGbtR39i32g9XyhHvGp6zn3oAYy5LWOc26pz62Kw L5DWMT++Pg7mJg= X-Received: by 2002:a05:6214:5191:b0:90e:81cd:787c with SMTP id 6a1803df08f44-90e929ae899mr90154766d6.29.1788260610966; Tue, 01 Sep 2026 04:03:30 -0700 (PDT) Received: from smtpclient.apple ([204.48.92.158]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-90ce4515130sm105829096d6.39.2026.09.01.04.03.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Sep 2026 04:03:30 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: Recovering a core dump deleted while debugging Date: Tue, 1 Sep 2026 07:03:19 -0400 Message-Id: References: <87v78u82xy.fsf@tromey.com> Cc: Philippe Blain via Gdb In-Reply-To: <87v78u82xy.fsf@tromey.com> To: Tom Tromey X-Mailer: iPhone Mail (22C152) X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Philippe Blain via Gdb Reply-To: Philippe Blain Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hi Tom, > Le 28 ao=C3=BBt 2026 =C3=A0 15:23, Tom Tromey a =C3=A9cri= t : >=20 > =EF=BB=BF >>=20 >> I=E2=80=99m debugging a core dump in GDB and some other process deleted t= he >> directory where the core dump was. Is there anyway to recover it? >=20 > Probably not. >=20 >> I tried 'lsof -p $pid' and looking in /proc/$pid/fd/ but the core dump >> does not appear there. I=E2=80=99m guessing GDB closes the file after it l= oads >> everything into memory ? >=20 > 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. >=20 > Checking /proc is pretty much the only thing I would have suggested. Thank you for answering. Indeed later I tried to continue my GDB session and= got a BFD error saying the core was not found.=20 Good news is we managed to reproduce and fix the failure leading to the core= dump :P Cheers, Philippe.=20