From: Simon Sobisch <simonsobisch@gnu.org>
To: gdb discussion list <gdb@sourceware.org>
Subject: GDB/MI - Possible missing stop-reason on attach or misleading documentation
Date: Thu, 3 Mar 2022 09:35:48 +0100 [thread overview]
Message-ID: <8a90c905-f238-0e14-ef7b-21c0eac58948@gnu.org> (raw)
When attaching to a running progress (that currently "waits" in
`getchar()`, but that likely doesn't matter) in async mode the following
records are returned:
=thread-group-started,id="i1",pid="12345"
=thread-created,id="1",group-id="i1"
=library-loaded,id=... many entries
~"0x00007fa0a626b7e0 in __read_nocancel () from /usr/lib64/libc.so.6\n"
*stopped,frame={addr="0x00007fa0a626b7e0",func="__read_nocancel",args=[],from="/usr/lib64/libc.so.6",arch="i386:x86-64"},thread-id="1",stopped-threads="all",core="1"
My understanding from
https://sourceware.org/gdb//onlinedocs/gdb/GDB_002fMI-Async-Records.html
was that the reason field is _always_ returned.
Questions:
* Did I look at the right place of the docs?
* Are all fields listed there should always be filled?
If not I highly suggest to add a note about that.
* Can the reason field be added in the attach case? I _guess_ that would
be either "location-reached" or "breakpoint-hit".
Simon
next reply other threads:[~2022-03-03 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 8:35 Simon Sobisch [this message]
2022-03-03 15:44 ` Simon Marchi
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=8a90c905-f238-0e14-ef7b-21c0eac58948@gnu.org \
--to=simonsobisch@gnu.org \
--cc=gdb@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).