This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/135: Move gdb_lasterr to ui_out?
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/135: Move gdb_lasterr to ui_out?
- From: ac131313 at cygnus dot com
- Date: 7 Jul 2001 03:00:51 -0000
- Reply-To: ac131313 at cygnus dot com
>Number: 135
>Category: gdb
>Synopsis: Move gdb_lasterr to ui_out?
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Fri Jul 06 20:08:02 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: ac131313@cygnus.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
Move gdb_lasterr to ui_out?
The way GDB throws errors and records them needs a re-think. ui_out
handles the correct output well. It doesn't resolve what to do with
output / error-messages when things go wrong.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: