This is the mail archive of the gdb-patches@sourceware.org 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: [RFA] Fix printing frame arguments for COFF debug info


> Date: Mon, 25 May 2009 15:55:37 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > > We're trying to recover nicely from the situation in order to be
> > > more useful for the user, so getting rid of the error is OK, but I'd
> > > probably still emit a complaint.  WDYT?
> > 
> > How about a warning under verbose operation?  Would that be enough?
> 
> Sure. I don't know what the verbose switch would be

I thought about info_verbose.

> I believe that complaints provide that kind of functionality - by
> default, complaints are turned off, but you can configure GDB to
> print the first N complaints emitted.

I looked into this, and I don't see a way to display a complaint in
this context.  The problem is that val_print is called a lot in the
middle of displaying arguments to functions, where a non-fatal warning
message cannot be reasonably displayed, especially if the message is
long.  Perhaps I'm missing something, but I don't see any machinery in
complaints.c (or elsewhere, for that matter) to handle such
situations.


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