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

From: Andrew Cagney <ac131313 at ges dot redhat dot com>
To: Daniel Jacobowitz <drow at mvista dot com>,Kevin Buettner <kevinb at redhat dot com>
Cc: gdb at sources dot redhat dot com
Date: Thu, 15 Aug 2002 21:36:20 -0400
Subject: Re: Issue an internal warning on first deprecated function call
References: <3D5C248D.4030003@ges.redhat.com> <1020815223303.ZM7495@localhost.localdomain> <20020816011518.GA24067@nevyn.them.org>

FYI,

The intent was for only one internal-warning message to appear per debug session. Given that an internal-warning message is pretty ``on-the-nose'' I don't think I could get away with any more than one.

I wrote:

> The problem behind this was discussed in:
> http://sources.redhat.com/ml/gdb/2001-03/msg00227.html

(recommended read)

> The idea is to issue an internal-warning on the first call to a > deprecated [multi-arch] function.

For architecture methods, it's pretty easy -- hook the ``set_gdbarch_deprecated...()'' calls. For things like write_register_bytes() it is less so.

enjoy,
Andrew

References:
- Issue an internal warning on first deprecated function call
  - From: Andrew Cagney
- Re: Issue an internal warning on first deprecated function call
  - From: Kevin Buettner
- Re: Issue an internal warning on first deprecated function call
  - From: Daniel Jacobowitz

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