From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Keith Seitz <keiths@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] Inferior stop events
Date: Thu, 14 Jun 2001 00:59:00 -0000
Message-id: <Pine.SUN.3.91.1010614110036.972L-100000@is>
References: <Pine.GSO.4.33.0106131332100.29122-100000@makita.cygnus.com>
X-SW-Source: 2001-06/msg00115.html

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?