public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/22925] gdb assumes target can activate threads at will, causes internal error in infrun.c in 'finish_step_over' Date: Sat, 31 Oct 2020 18:00:24 +0000 [thread overview] Message-ID: <bug-22925-4717-g8ZxOMTHBp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-22925-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=22925 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot org --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- I'm a little confused on this one. On the one hand -- the remote protocol doesn't have a way for a target to explain that it isn't in control of scheduling. This could be added, but only with some cooperation from gdb as well. However in the example you did: (gdb) b (gdb) c Doesn't that "b" set a breakpoint? Then "continue" has to step off the breakpoint. This is done by single-stepping, I suppose because setting another breakpoint is difficult -- gdb or gdbserver would have to decode instructions to find the next instruction. -- You are receiving this mail because: You are on the CC list for the bug.
next parent reply other threads:[~2020-10-31 18:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-22925-4717@http.sourceware.org/bugzilla/> 2020-10-31 18:00 ` tromey at sourceware dot org [this message] 2022-11-29 19:38 ` tromey at sourceware dot org
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=bug-22925-4717-g8ZxOMTHBp@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).