public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/13587] New: stop reasons and other info missing from events.stop
Date: Wed, 11 Jan 2012 16:52:00 -0000 [thread overview]
Message-ID: <bug-13587-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13587
Bug #: 13587
Summary: stop reasons and other info missing from events.stop
Product: gdb
Version: unknown
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: tromey@redhat.com
Classification: Unclassified
The stop events emitted by events.stop do not include all the
info available to MI.
See PR 8444 for some information.
See PR 11688 for some patches to hook ui-out to Python.
Probably the Python code here should be mimicking MI and calling bpstat_print.
This may involve some refactoring to change how the proper event class
is determined.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-01-11 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 16:52 tromey at redhat dot com [this message]
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
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@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).