public inbox for
 help / color / mirror / Atom feed
From: Simon Sobisch <>
To: gdb discussion list <>
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: <> (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:

=library-loaded,id=... many entries
~"0x00007fa0a626b7e0 in __read_nocancel () from /usr/lib64/\n"

My understanding from 
was that the reason field is _always_ returned.

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


             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:

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