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:00:40 +0000	[thread overview]
Message-ID: <bug-27908-4717-pC2mSst8bd@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 #5 from Tom de Vries <vries at gcc dot gnu.org> ---
I put a breakpoint in fputs and continued to the point that the thread 2
message is printed:
...
(gdb) bt
#0  __GI__IO_fputs (str=0x17eda24 <get_print_cell()::buf+100> "2", 
    fp=0x7ffff51a35a0 <_IO_2_1_stdout_>) at iofputs.c:32
#1  0x0000000000b11d2d in stdio_file::puts (this=0x1a542e0, 
    linebuffer=0x17eda24 <get_print_cell()::buf+100> "2")
    at /home/vries/gdb_versions/devel/src/gdb/ui-file.c:247
#2  0x0000000000b4995f in fputs_maybe_filtered (
    linebuffer=0x17eda24 <get_print_cell()::buf+100> "2", stream=0x1a542e0,
filter=1)
    at /home/vries/gdb_versions/devel/src/gdb/utils.c:1731
#3  0x0000000000b49e3c in fputs_styled (
    linebuffer=0x17eda24 <get_print_cell()::buf+100> "2", style=...,
stream=0x1a542e0)
    at /home/vries/gdb_versions/devel/src/gdb/utils.c:1912
#4  0x000000000058b06b in cli_ui_out::do_field_string (this=0x1adce00, fldno=2,
width=0, 
    align=ui_noalign, fldname=0xf3a84d "thread-id", 
    string=0x17eda24 <get_print_cell()::buf+100> "2", style=...)
    at /home/vries/gdb_versions/devel/src/gdb/cli-out.c:177
#5  0x0000000000b131b0 in ui_out::field_string (this=0x1adce00, 
    fldname=0xf3a84d "thread-id", string=0x17eda24 <get_print_cell()::buf+100>
"2", 
    style=...) at /home/vries/gdb_versions/devel/src/gdb/ui-out.c:527
#6  0x00000000007c2a9e in print_signal_received_reason (uiout=0x1adce00, 
    siggnal=GDB_SIGNAL_0) at
/home/vries/gdb_versions/devel/src/gdb/infrun.c:8263
#7  0x0000000000af2fd6 in tui_on_signal_received (siggnal=GDB_SIGNAL_0)
    at /home/vries/gdb_versions/devel/src/gdb/tui/tui-interp.c:114
#8  0x000000000059fb6c in std::__invoke_impl<void, void (*&)(gdb_signal),
gdb_signal> (
    __f=@0x19eaaa0: 0xaf2f6c <tui_on_signal_received(gdb_signal)>)
    at /usr/include/c++/10/bits/invoke.h:60
#9  0x000000000059efd9 in std::__invoke_r<void, void (*&)(gdb_signal),
gdb_signal> (
    __fn=@0x19eaaa0: 0xaf2f6c <tui_on_signal_received(gdb_signal)>)
    at /usr/include/c++/10/bits/invoke.h:153
#10 0x000000000059ead6 in std::_Function_handler<void (gdb_signal), void
(*)(gdb_signal)>::_M_invoke(std::_Any_data const&, gdb_signal&&)
(__functor=..., 
    __args#0=@0x7fffffffd3a4: GDB_SIGNAL_0) at
/usr/include/c++/10/bits/std_function.h:291
#11 0x00000000007c80ee in std::function<void
(gdb_signal)>::operator()(gdb_signal) const (
    this=0x19eaaa0, __args#0=GDB_SIGNAL_0) at
/usr/include/c++/10/bits/std_function.h:622
#12 0x00000000007c75cd in gdb::observers::observable<gdb_signal>::notify (
    this=0x17c0b80 <gdb::observers::signal_received>, args#0=GDB_SIGNAL_0)
    at /home/vries/gdb_versions/devel/src/gdb/../gdbsupport/observable.h:150
#13 0x00000000007c3420 in normal_stop ()
    at /home/vries/gdb_versions/devel/src/gdb/infrun.c:8527
#14 0x00000000007b93b0 in fetch_inferior_event ()
    at /home/vries/gdb_versions/devel/src/gdb/infrun.c:4144
#15 0x000000000079d2a7 in inferior_event_handler (event_type=INF_REG_EVENT)
    at /home/vries/gdb_versions/devel/src/gdb/inf-loop.c:41
#16 0x00000000007c4eb4 in infrun_async_inferior_event_handler (data=0x0)
    at /home/vries/gdb_versions/devel/src/gdb/infrun.c:9423
#17 0x00000000004dc498 in check_async_event_handlers ()
    at /home/vries/gdb_versions/devel/src/gdb/async-event.c:335
#18 0x0000000000e1ea74 in gdb_do_one_event ()
    at /home/vries/gdb_versions/devel/src/gdbsupport/event-loop.cc:216
#19 0x00000000008292ba in start_event_loop ()
    at /home/vries/gdb_versions/devel/src/gdb/main.c:421
#20 0x00000000008293d9 in captured_command_loop ()
    at /home/vries/gdb_versions/devel/src/gdb/main.c:481
#21 0x000000000082abe4 in captured_main (data=0x7fffffffda30)
    at /home/vries/gdb_versions/devel/src/gdb/main.c:1353
#22 0x000000000082ac4a in gdb_main (args=0x7fffffffda30)
    at /home/vries/gdb_versions/devel/src/gdb/main.c:1368
#23 0x00000000004178dd in main (argc=12, argv=0x7fffffffdb38)
    at /home/vries/gdb_versions/devel/src/gdb/gdb.c:32
...

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

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