This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA]: issue warnings for frame offenses
- From: Jeff Johnston <jjohnstn at redhat dot com>
- To: Jeff Johnston <jjohnstn at redhat dot com>
- Cc: Andrew Cagney <cagney at gnu dot org>, Joel Brobecker <brobecker at gnat dot com>, gdb-patches at sources dot redhat dot com
- Date: Thu, 04 Nov 2004 13:28:12 -0500
- Subject: Re: [RFA]: issue warnings for frame offenses
- References: <417EBFF9.5060104@redhat.com> <20041026213037.GR1039@gnat.com> <41897333.6070201@gnu.org> <418A58F3.8000603@redhat.com>
Jeff Johnston wrote:
Sounds fine. I'll start working on it. I assume you meant
non_fatal_error below for the new function that issues the quit.
Ignore my question above. I understand what is asked for now. I was reading
QUIT as being QUIT the current operation, but you mean it to be more severe so
what you say below makes sense.
-- Jeff J.
- add a new fatal_error():
There should be a new error mechanism that throws a QUIT instead of
ERROR. Code should not normally be catching QUIT (much unfortunately
does). A fatal error is things like: syntax error; no target; lost
target. Things like a memory access violation though are not fatal.
- think about stopping code catching and then discarding QUIT
Grep for RETURN_MASK_ALL in the sources - it should be
RETURN_MASK_ERROR :-/
- modify the backtrace code to catch ERROR, but not QUIT
Along the lines of Joel's suggestion, the backtrace command should
catch ERROR (but should not catch QUIT). That way simple problems
don't abort the script but fatal ones do.