From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id gBFDCjAXkGT99QcAWB0awg (envelope-from ) for ; Mon, 19 Jun 2023 04:52:00 -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=NLl0Mu3k; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 1B4D11E0BB; Mon, 19 Jun 2023 04:52:00 -0400 (EDT) Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 0ADEA1E0AC for ; Mon, 19 Jun 2023 04:51:58 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 923A2385828D for ; Mon, 19 Jun 2023 08:51:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 923A2385828D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1687164717; bh=9pxNqM1UMtlXqFF/sMMg/rhJIjzdB/IoMZ5OpLp0dc0=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=NLl0Mu3kcpmYcudksJX7WQHTVjY8PzCWStPuxG0zVLcvh8Y/l+2ax/Y/rGQdv65un oIwkSZPwX0wYRGO6CytS4eeNa2lrrncvV/sUbxtrImobyzzZCHYAZ/djjAZcP2pWqe M0hPrHUqvavryW/mQAzT8gYuadK9CtBKVTTspM9s= Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) by sourceware.org (Postfix) with ESMTPS id E086B3858D28 for ; Mon, 19 Jun 2023 08:51:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org E086B3858D28 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-988f066f665so6769366b.2 for ; Mon, 19 Jun 2023 01:51:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687164688; x=1689756688; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ja6hxs1qSQezNgyTOaEGCMwbWyJ1XM2sRFm7fZvpuF4=; b=VPSPPiw2Dw1khHzhGYXFhh30BCtLZtTn9owtgf5YQq6TfORI4+W5EoXRG7g7scKbDm djdw3UPr/B9qo+pwze2GV+vBRpIaKQLdEWzdDM+GPQvTyJRa5jDBzkqkqvT5YCbipqM5 oW4sk8OQHV+vJzNnTOoPe06snfEZEseaU/+99hP+bSeE6Vxht1iWTxEliF6xo3gQC3KT toWhRnLf7hlQvgtZ6RZBFduWv4qhWrMQUtVLvqMkYURLoBwELXDKTCMfJCoIaxAuIiVT WjYW5XwiwfywxtjY7pV+PA5uOc4igKmgQ2H5rWPZQupeyST5lpUKbyGKfvnyGOiWqYB/ gYow== X-Gm-Message-State: AC+VfDzt0nVQXxvAraClkkkJYspFF46RSxsW5J+8yeEgYf+9mw8BiTG1 wcn0gxjmeoZ9U6zAFv7h29Q9cmIH7aXRZCNTQMGAXknnvus= X-Google-Smtp-Source: ACHHUZ7eJiuuiMip4G4i/dNdUE1ZkaRNWkmmqM24LX0QUHi1MOFRtQjPQ4PkIM+aKK02v+gdf6lBn9l5F5CQJesVIV4= X-Received: by 2002:a17:907:368c:b0:982:2586:f85 with SMTP id bi12-20020a170907368c00b0098225860f85mr8233790ejc.65.1687164688169; Mon, 19 Jun 2023 01:51:28 -0700 (PDT) MIME-Version: 1.0 Date: Mon, 19 Jun 2023 10:51:17 +0200 Message-ID: Subject: GDB does not work on DMTCP restart. To: gdb@sourceware.org X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Piotr Czak via Gdb Reply-To: Piotr Czak Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" Hello everyone, My name is Piotr and I'd like to ask for suggestions and help with one issue I have. I'm using DMTCP to save a checkpoint of some applications and restart from it. In some cases I need to use gdb to debug issues. I noticed that in one design gdb does not see debug symbols when used after the restart from a checkpoint. It works on "save" when executed under the DMTCP when the checkpoint is created but not after restarting from it. This is happening only on some tests to which I have limited access. In that case gdb cannot connect current application location with sources, it shows me wrong but always the same location. I can set a breakpoint but it is never hit even if I know that this part of the code is executed. From the log I see that gdb thinks that my function is in some file which is not correct. If I remember well, the line number in the log message was correct. I also cannot display variables. The result of sharedlibrary command is empty. In case of issues I'm not able to do any debugging. All of these debug features work when I try to save DMTCP checkpoint. Unfortunately, since it is related to my work I cannot provide more detailed information but I will be grateful if you could provide me with some suggestions what could be a reason for the issue or how to debug the issue. Thanks, Best Regards, Piotr