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 09:25:16 +0000	[thread overview]
Message-ID: <bug-27908-4717-oK3Y3Vd6dx@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 #4 from Tom de Vries <vries at gcc dot gnu.org> ---
Using this trick:
...
$ git diff
diff --git a/gdb/testsuite/gdb.base/run-attach-while-running.exp
b/gdb/testsuite/gdb.base/r
un-attach-while-running.exp
index 7c16aa6f5c4..230ad66ee73 100644
--- a/gdb/testsuite/gdb.base/run-attach-while-running.exp
+++ b/gdb/testsuite/gdb.base/run-attach-while-running.exp
@@ -93,6 +93,8 @@ proc_with_prefix test { non-stop threaded run-or-attach } {

        gdb_test "attach $test_pid" "Attaching to program: .*" "attach to
process"

+       gdb_test "echo bla\\n"
+
        gdb_exit
        kill_wait_spawned_process $test_spawn_id
     } else {
...
we can see the extra message in the PASS case as well:
...
Reading symbols from
/usr/lib/debug/lib64/ld-2.26.so-2.26-lp152.26.6.1.x86_64.debug...^M
0x00007f5eeb0554c0 in __GI___nanosleep
(requested_time=requested_time@entry=0x7fff7b78a1c0,
remaining=remaining@entry=0x7fff7b78a1c0) at
../sysdeps/unix/sysv/linux/nanosleep.c:27^M
27        return SYSCALL_CANCEL (nanosleep, requested_time, remaining);^M
(gdb) PASS: gdb.base/run-attach-while-running.exp: threaded=1:
run-or-attach=attach: non-stop=on: test: attach to process
^M
Thread 2 "run-attach-whil" stopped.^M
0x00007f5eeb0554c0 in __GI___nanosleep
(requested_time=requested_time@entry=0x7f5eeaf8aea0,
remaining=remaining@entry=0x7f5eeaf8aea0) at
../sysdeps/unix/sysv/linux/nanosleep.c:27^M
27        return SYSCALL_CANCEL (nanosleep, requested_time, remaining);^M
echo bla\n^M
bla^M
(gdb) PASS: gdb.base/run-attach-while-running.exp: threaded=1:
run-or-attach=attach: non-stop=on: test: echo bla\n
...

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

  parent reply	other threads:[~2021-05-25  9:25 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 [this message]
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
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-oK3Y3Vd6dx@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).