Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix printing frame arguments for COFF debug info
Date: Mon, 25 May 2009 06:29:00 -0000	[thread overview]
Message-ID: <20090525062922.GE23016@adacore.com> (raw)
In-Reply-To: <83iqjst89t.fsf@gnu.org>

> 2009-05-23  Eli Zaretskii  <eliz@gnu.org>
> 
> 	* valprint.c (val_print): If LANGUAGE is "unknown" or "auto" or
> 	"local", fall back on current_language.

The patch looks good, although I'm still unconvinced that it is actually
necessary.  I'm slightly worried about the potential for feeding an
expression to the wrong language (as we've seen a crash a long time
ago when feeding some C++ stuff thinking it was Ada), but we can
actually look into that if it ever happens.

One of the things that you patch does, is also hidding an error that
was actually an internal error.  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?

> --- valprint.c~0	2009-03-21 07:03:53.000000000 +0200
> +++ valprint.c	2009-05-23 13:33:14.062500000 +0300
> @@ -257,6 +257,14 @@ val_print (struct type *type, const gdb_
>        return (0);
>      }
>  
> +  /* If the LANGUAGE argument we received is one of the placeholder
> +     ``languages'', its la_val_print method will throw an error.  To
> +     avoiding that, try falling back on current_language.  */
        ^^^ avoid

-- 
Joel


  reply	other threads:[~2009-05-25  6:29 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 [this message]
2009-05-25 20:41           ` Eli Zaretskii
2009-05-25 22:55             ` Joel Brobecker
2009-05-29 12:07               ` Eli Zaretskii
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=20090525062922.GE23016@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --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