From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix printing frame arguments for COFF debug info
Date: Fri, 29 May 2009 12:07:00 -0000 [thread overview]
Message-ID: <83skio3yft.fsf@gnu.org> (raw)
In-Reply-To: <20090525225537.GH23016@adacore.com>
> 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.
next prev parent reply other threads:[~2009-05-29 12:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 16:51 Eli Zaretskii
2009-05-16 18:00 ` More problems with language in printing symbols Eli Zaretskii
2009-05-17 16:17 ` [RFA] " Eli Zaretskii
2009-05-20 23:07 ` Joel Brobecker
2009-05-23 9:26 ` Eli Zaretskii
2009-05-20 23:07 ` [RFA] Fix printing frame arguments for COFF debug info Joel Brobecker
2009-05-21 3:22 ` Eli Zaretskii
2009-05-21 17:05 ` Joel Brobecker
2009-05-23 10:37 ` Eli Zaretskii
2009-05-25 6:29 ` Joel Brobecker
2009-05-25 20:41 ` Eli Zaretskii
2009-05-25 22:55 ` Joel Brobecker
2009-05-29 12:07 ` Eli Zaretskii [this message]
2009-05-23 9:33 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83skio3yft.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox