From: Piotr Czak <piotr.czak@gmail.com>
To: gdb@sourceware.org
Subject: GDB does not work on DMTCP restart.
Date: Mon, 19 Jun 2023 10:51:17 +0200 [thread overview]
Message-ID: <CAEk01YbCTfOp0WoEAw1hgxAkAzkYe8ndEh3+JD1pNSMjen17Pw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
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
next reply other threads:[~2023-06-19 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 8:51 Piotr Czak [this message]
2023-06-28 21:52 ` Magne Hov
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=CAEk01YbCTfOp0WoEAw1hgxAkAzkYe8ndEh3+JD1pNSMjen17Pw@mail.gmail.com \
--to=piotr.czak@gmail.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).