public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/13587] stop reasons and other info missing from events.stop
Date: Mon, 11 Dec 2023 18:43:33 +0000 [thread overview]
Message-ID: <bug-13587-4717-eqXuLstMu2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13587-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13587
--- Comment #5 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e187e7c9696fbf66cf25d5fb8113bc3bc06b9e8b
commit e187e7c9696fbf66cf25d5fb8113bc3bc06b9e8b
Author: Tom Tromey <tromey@adacore.com>
Date: Fri Nov 3 13:23:41 2023 -0600
Emit stop reason details in Python stop events
This changes Python stop events to carry a "details" dictionary, that
holds any relevant information about the stop. The details are
constructed using more or less the same procedure as is done for MI.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=13587
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-11 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 16:52 [Bug python/13587] New: " tromey at redhat dot com
2012-08-24 15:18 ` [Bug python/13587] " alex-sourceware at spamt dot net
2012-08-24 16:39 ` alex-sourceware at spamt dot net
2012-08-24 16:41 ` alex-sourceware at spamt dot net
2023-11-14 18:37 ` tromey at sourceware dot org
2023-11-14 19:26 ` tromey at sourceware dot org
2023-12-11 18:43 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-11 18:44 ` tromey at sourceware dot 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-13587-4717-eqXuLstMu2@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).