public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/28375] New: Cannot find user-level thread for LWP: generic error
Date: Wed, 22 Sep 2021 12:38:58 +0000	[thread overview]
Message-ID: <bug-28375-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 28375
           Summary: Cannot find user-level thread for LWP: generic error
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

With patch:
...
diff --git a/gdb/testsuite/gdb.threads/process-dies-while-detaching.exp
b/gdb/testsuite/gdb
.threads/process-dies-while-detaching.exp
index ac1aad26ec5..3b59afb2fcf 100644
--- a/gdb/testsuite/gdb.threads/process-dies-while-detaching.exp
+++ b/gdb/testsuite/gdb.threads/process-dies-while-detaching.exp
@@ -240,6 +240,7 @@ proc test_detach_watch {multi_process cmd} {
        global binfile decimal

        clean_restart ${binfile}
+       gdb_test_no_output "set can-use-hw-watchpoints 0"

        if ![runto_main] {
            fail "can't run to main"
@@ -255,14 +256,16 @@ proc test_detach_watch {multi_process cmd} {
        }

        # Set a watchpoint in the child.
-       gdb_test "watch globalvar" ".* watchpoint $decimal: globalvar"
+       gdb_test "watch globalvar" "Watchpoint $decimal: globalvar"

        # Continue to the _exit breakpoint.  This arms the watchpoint
        # registers in all threads.  Detaching will thus need to clear
        # them out, and handle the case of the thread disappearing
        # while doing that (on targets that need to detach from each
        # thread individually).
-       continue_to_exit_bp
+       with_timeout_factor 100 {
+           continue_to_exit_bp
+       }

        do_detach $multi_process $cmd "normal"
     }
...
we run into:
...
(gdb) PASS: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue to breakpoint: _exit
continue^M
Continuing.^M
Cannot find user-level thread for LWP 10324: generic error^M
(gdb) FAIL: gdb.threads/process-dies-while-detaching.exp: single-process:
continue: watchpoint: continue
...

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

             reply	other threads:[~2021-09-22 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 12:38 vries at gcc dot gnu.org [this message]
2024-07-29 11:52 ` [Bug threads/28375] " luis.machado at arm dot com
2024-07-29 13:27 ` vries at gcc dot gnu.org
2024-07-29 14:08 ` luis.machado at arm dot com

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-28375-4717@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).