From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: "psmith@gnu.org" <psmith@gnu.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: Tools to debug multiple cores/processes at the same time?
Date: Fri, 20 Aug 2021 06:28:25 +0000 [thread overview]
Message-ID: <SN6PR11MB28935BEAE83B5B424023EF0BC4C19@SN6PR11MB2893.namprd11.prod.outlook.com> (raw)
In-Reply-To: <e4cddda40744058c216fb4373ede3ec3f0a0cbb5.camel@gnu.org>
> Let me give an example of a debugging session:
>
> * start a session with 3 core files
>
> * run a command that shows info about each core (assume a python
> "showinfo" command that show all threads with some details about each
> one). Maybe a command like:
> (gdb) all: showinfo
> i1: <info>
> i2: <info>
> i3: <info>
>
> * For each core, go to a certain thread (of course the thread numbers
> will be different in each core):
> (gdb) i1: thr 7
> (gdb) i2: thr 9
> (gdb) i3: thr 23
>
> * Run a command that returns some value and stores it in a convenience
> variable, on all cores:
> (gdb) all: set $v = $findstuff()
>
> * Run a command that shows some value, on all cores:
> (gdb) all: p $v->someDetail
> i1: $1 = 7
> i2: $1 = 44
> i3: $1 = 165
>
> I dunno, something like that. Alternatively maybe it would be simpler
> for output for each inferior to go to a separate terminal or whatever.
Hi,
Have you considered using the "thread apply" command?
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2021-08-20 6:28 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
2021-08-18 21:09 ` Paul Smith
2021-08-19 10:56 ` Philippe Waroquiers
2021-08-20 6:28 ` Aktemur, Tankut Baris [this message]
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=SN6PR11MB28935BEAE83B5B424023EF0BC4C19@SN6PR11MB2893.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.com \
--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).