This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Issue an internal warning on first deprecated function call

On Aug 21, 11:21am, Andrew Cagney wrote:

> > It's not a grave problem? Please explain.
> 
> Eli's right here.  The warning would be to strong.
> 
> internal-error and internal-warning refer to GDB detecting an errenous 
> internal state.  Error for non-recoverable, warning for recoverable.
> 
> Unless some action is taken, the long term prognosis doesn't look good. 

Wait a moment...  You were going to use internal warnings to alert the
users that a deprecated function has been called, right?  I don't
consider this to be an erroneous internal state that has to be
recovered from.

>   However, short term, GDB could just as easily die due to a SIGSEG.

It shouldn't so long as the gdb developers haven't broken the legacy
functions that are being deprecated.  (Unless it did before, but that's
a different problem.)

Kevin
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]