This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] Inferior stop events
- To: Keith Seitz <keiths at cygnus dot com>
- Subject: Re: [RFC] Inferior stop events
- From: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Date: Thu, 14 Jun 2001 11:00:57 +0300 (IDT)
- cc: gdb at sources dot redhat dot com
On Wed, 13 Jun 2001, Keith Seitz wrote:
> Mailing-List: contact gdb-help@sourceware.cygnus.com; run by ezmlm
> Sender: gdb-owner@sources.redhat.com
> X-Authentication-Warning: makita.cygnus.com: keiths owned process doing -bs
> Date: Wed, 13 Jun 2001 13:45:36 -0700 (PDT)
> From: Keith Seitz <keiths@cygnus.com>
>
> Hi,
>
> The next part of my ongoing quest to get information out of gdb:
> inferior_stop events. These events are to inform a UI that the inferior
> has stopped running and why it has stopped.
>
> I propose to take "enum stop_reason" from infrun.c and move it into
> inferior.h. This enum will be used by both print_stop_reason (which is
> really a cli function) and user interfaces, like Insight. (Pretend I
> didn't say that.)
>
> It is then my intention to litter infrun.c with event notifications, which
> provide a reason for the stop, and some supplemental info on the stop
> (signal, exit status, breakpoint#, etc).
For the benefit of the GUI-challenged people such as myself: how, if at
all, is this done now? That is, what does a typical UI for GDB do to
tell the user why did the debuggee stopped?