This is the mail archive of the
mailing list for the GDB project.
Re: [RFA]: error_silent for use in pending breakpoint support
- From: "J. Johnston" <jjohnstn at redhat dot com>
- To: Jeff Johnston <jjohnstn at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com,Elena Zannoni <ezannoni at redhat dot com>
- Date: Fri, 09 Jan 2004 13:55:14 -0500
- Subject: Re: [RFA]: error_silent for use in pending breakpoint support
- Organization: Red Hat Inc.
- References: <3FE21F2B.firstname.lastname@example.org>
Jeff Johnston wrote:
To properly support pending breakpoints, gdb needs to be able to
suppress the "not found" messages at will, but it also needs to
sometimes issue these messages and determine the cause of the error was
a "not found" event.
To handle the problem, I propose two new useful functions in utils.c.
The first is error_silent() which works just like error(), only it does
not issue the error message. Like error(), it stores the error message
in gdb_lasterr. This leads to the other new function:
error_last_output() which is used to output the last error message.
This allows the pending breakpoint support to issue the error message
when the user is doing the initial break command and to suppress it when
shared libraries are being loaded or a pending breakpoint is reenabled.
Ok to commit?
2003-12-18 Jeff Johnston <email@example.com>
* linespec.c (decode_variable, symtab_from_filename): Call
error_silent with error message instead of throwing an exception
* defs.h (error_silent, error_last_output): Add prototypes.
* utils.c (error_silent, error_last_output): New functions.