public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Adrian Oltean <adrian.oltean@nxp.com>
To: Luis Machado <luis.machado@arm.com>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: [EXT] Re: Context switch during stepping causes weird behavior
Date: Wed, 12 Oct 2022 06:40:11 +0000	[thread overview]
Message-ID: <AM6PR04MB4630AD0335748D365C6CE6E4F1229@AM6PR04MB4630.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <18edddf7-6779-96e1-2ed2-facaf7bea2d9@arm.com>

Hi Luis,

Indeed, GDB does not handle very well such a case... 

I'll have to think about your suggestion. The idea is not bad but my GDB server is not
aware about the underlying debugged app (Linux kernel), thus making it complicated
to map kernel threads from target to actual GDB threads.

Thanks,
Adrian

> -----Original Message-----

> GDB doesn't really like things changing behind its back, and I don't think this case
> is handled very well (or at all).
> 
> When the thread migrates to a different core, would it be possible to re-order
> the thread numbering so GDB's view of the threads is unchanged?

      reply	other threads:[~2022-10-12  6:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04 12:19 Adrian Oltean
2022-10-04 16:57 ` John Baldwin
2022-10-05  6:48   ` Adrian Oltean
2022-10-05 16:53     ` John Baldwin
2022-10-07 15:40       ` Keith Seitz
2022-10-12  6:46         ` [EXT] " Adrian Oltean
2022-10-13  6:34           ` Luis Machado
2022-10-13  6:41             ` Adrian Oltean
2022-10-10  9:52 ` Luis Machado
2022-10-12  6:40   ` Adrian Oltean [this message]

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=AM6PR04MB4630AD0335748D365C6CE6E4F1229@AM6PR04MB4630.eurprd04.prod.outlook.com \
    --to=adrian.oltean@nxp.com \
    --cc=gdb@sourceware.org \
    --cc=luis.machado@arm.com \
    /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).