public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27830] Attempt to resume already running thread
Date: Fri, 07 May 2021 14:26:33 +0000	[thread overview]
Message-ID: <bug-27830-4717-j6MykoOCwr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27830-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27830

--- Comment #1 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
The error can be reproduced with the native target too.  In the reproducer
replace gdb.in.cmd with:

 set height 0
 set trace-commands on
 set non-stop on
 set displaced-stepping off
 file thr.x
 starti
 break main

Then when you run make you'll see:

  $ make
  ... snip ...
  +stepi
  [New Thread 0x7ffff7ff8700 (LWP 3889982)]
  Hello from the thread.
  cmd.gdb:14: Error in sourced command file:
  Couldn't get registers: No such process.
  **** FAILED ****

Despite the 'no such process' message, I think this is the same issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2021-05-07 14:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 14:16 [Bug gdb/27830] New: " andrew.burgess at embecosm dot com
2021-05-07 14:26 ` andrew.burgess at embecosm dot com [this message]
2021-05-10 17:27 ` [Bug gdb/27830] " andrew.burgess at embecosm dot com
2021-05-10 19:24 ` andrew.burgess at embecosm dot com
2022-06-21 11:28 ` pedro at palves dot net
2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org
2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org
2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org
2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org
2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org
2023-11-13 15:00 ` pedro at palves dot net

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-27830-4717-j6MykoOCwr@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: 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).