public inbox for
 help / color / mirror / Atom feed
From: Simon Marchi <>
To: Simon Sobisch <>,
	gdb discussion list <>
Subject: Re: GDB/MI - Possible missing stop-reason on attach or misleading documentation
Date: Thu, 3 Mar 2022 10:44:24 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022-03-03 03:35, Simon Sobisch via Gdb wrote:
> 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/\n"
> *stopped,frame={addr="0x00007fa0a626b7e0",func="__read_nocancel",args=[],from="/usr/lib64/",arch="i386:x86-64"},thread-id="1",stopped-threads="all",core="1"
> My understanding from
> was that the reason field is _always_ returned.
> Questions:
> * Did I look at the right place of the docs?

I think so.

> * Are all fields listed there should always be filled?

If it doesn't say otherwise, yes.  This looks like a bug.

>   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".

Or signal-received, same as you get when GDB interrupts a running thread
after the user does ^C.  It depends on the status the target returns.
Attaching is kind of like the user requesting the attached process to


      reply	other threads:[~2022-03-03 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03  8:35 Simon Sobisch
2022-03-03 15:44 ` Simon Marchi [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).