From: Paul Koning <paulkoning@comcast.net>
To: psmith@gnu.org
Cc: gdb@sourceware.org
Subject: Re: Tools to debug multiple cores/processes at the same time?
Date: Wed, 18 Aug 2021 16:53:43 -0400 [thread overview]
Message-ID: <97D56F18-F336-45CD-9258-CB884C7F76E5@comcast.net> (raw)
In-Reply-To: <3ba28620390947de2a84cabbd1958852aad97d5e.camel@gnu.org>
> On Aug 18, 2021, at 3:55 PM, Paul Smith via Gdb <gdb@sourceware.org> wrote:
>
> In my environment I'm working on a distributed system where the same
> process is running on a number of different systems. The way these
> processes work is that they should all have (approximately) the same
> set of in-memory content at the same time.
> ...
> What I'm really wondering is, has anyone heard of something like this,
> or is there any support (even partial support) for something like this
> in GDB today? I get that it seems like a somewhat specialized request.
>
> Debugging multiple live processes at the same time would also be great,
> of course.
There is multiple target support, which I haven't had a chance to try yet but from what I remember reading is a recently added GDB feature. It should handle your case plus even stranger ones, such as multiple processes running different code, or even running on different instruction sets. It's just what you need for debugging distributed applications.
paul
next prev parent reply other threads:[~2021-08-18 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 19:55 Paul Smith
2021-08-18 20:25 ` John Baldwin
2021-08-18 20:53 ` Paul Koning [this message]
2021-08-18 21:09 ` Paul Smith
2021-08-19 10:56 ` Philippe Waroquiers
2021-08-20 6:28 ` Aktemur, Tankut Baris
2021-08-19 11:04 ` Andrew Burgess
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=97D56F18-F336-45CD-9258-CB884C7F76E5@comcast.net \
--to=paulkoning@comcast.net \
--cc=gdb@sourceware.org \
--cc=psmith@gnu.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).