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 gdb/27908] FAIL: gdb.base/run-attach-while-running.exp: threaded=1: run-or-attach=attach: non-stop=on: test: attach to process (timeout) Date: Tue, 25 May 2021 10:18:16 +0000 [thread overview] Message-ID: <bug-27908-4717-WYAZzWLiaW@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27908-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27908 --- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> --- Debugging setup using just an attach: ... $ cat gdb.in set non-stop on set height 0 set width 0 set confirm off $ cat ./exp.sh #!/bin/sh ./outputs/gdb.base/run-attach-while-running/run-attach-while-running-threads & pid=$! cat gdb.in > gdb.cmd echo attach $pid >> gdb.cmd echo "info threads" >> gdb.cmd ./gdb -q -x gdb.cmd ... Run exp.sh script and type info threads: ... $ ./exp.sh [New LWP 22236] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007f3ff816c4c0 in __GI___nanosleep (requested_time=requested_time@entry=0x7ffeb63936c0, remaining=remaining@entry=0x7ffeb63936c0) at ../sysdeps/unix/sysv/linux/nanosleep.c:27 27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining); Id Target Id Frame * 1 Thread 0x7f3ff8bab740 (LWP 22234) "run-attach-whil" 0x00007f3ff816c4c0 in __GI___nanosleep (requested_time=requested_time@entry=0x7ffeb63936c0, remaining=remaining@entry=0x7ffeb63936c0) at ../sysdeps/unix/sysv/linux/nanosleep.c:27 2 Thread 0x7f3ff80a2700 (LWP 22236) "run-attach-whil" (running) (gdb) Thread 2 "run-attach-whil" stopped. 0x00007f3ff816c4c0 in __GI___nanosleep (requested_time=requested_time@entry=0x7f3ff80a1ea0, remaining=remaining@entry=0x7f3ff80a1ea0) at ../sysdeps/unix/sysv/linux/nanosleep.c:27 27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining); info threads Id Target Id Frame * 1 Thread 0x7f3ff8bab740 (LWP 22234) "run-attach-whil" 0x00007f3ff816c4c0 in __GI___nanosleep (requested_time=requested_time@entry=0x7ffeb63936c0, remaining=remaining@entry=0x7ffeb63936c0) at ../sysdeps/unix/sysv/linux/nanosleep.c:27 2 Thread 0x7f3ff80a2700 (LWP 22236) "run-attach-whil" 0x00007f3ff816c4c0 in __GI___nanosleep (requested_time=requested_time@entry=0x7f3ff80a1ea0, remaining=remaining@entry=0x7f3ff80a1ea0) at ../sysdeps/unix/sysv/linux/nanosleep.c:27 (gdb) ... We can see that thread 2 initially is still running, then the thread stopped message arrives, and then info threads shows that the thread is no longer running. So why did it stop? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-25 10:18 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-25 8:44 [Bug gdb/27908] New: " vries at gcc dot gnu.org 2021-05-25 8:46 ` [Bug gdb/27908] " vries at gcc dot gnu.org 2021-05-25 8:47 ` vries at gcc dot gnu.org 2021-05-25 9:13 ` vries at gcc dot gnu.org 2021-05-25 9:25 ` vries at gcc dot gnu.org 2021-05-25 9:25 ` vries at gcc dot gnu.org 2021-05-25 10:00 ` vries at gcc dot gnu.org 2021-05-25 10:06 ` vries at gcc dot gnu.org 2021-05-25 10:18 ` vries at gcc dot gnu.org [this message] 2021-05-25 11:37 ` vries at gcc dot gnu.org 2021-05-25 12:35 ` vries at gcc dot gnu.org 2021-06-07 13:29 ` [Bug testsuite/27908] " vries at gcc dot gnu.org 2021-06-07 13:46 ` cvs-commit at gcc dot gnu.org 2021-06-07 13:47 ` vries at gcc dot gnu.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-27908-4717-WYAZzWLiaW@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).