From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [RFA] stabsread.c (define_symbol): Guard against bad stabstring input.
Date: Sat, 05 Mar 2011 00:49:00 -0000 [thread overview]
Message-ID: <201103050049.14785.pedro@codesourcery.com> (raw)
In-Reply-To: <201103050042.59285.pedro@codesourcery.com>
On Saturday 05 March 2011 00:42:59, Pedro Alves wrote:
> On Saturday 05 March 2011 00:37:25, Michael Snyder wrote:
> > I think I heard someone say that gdb should be proof against all inputs?
>
> Yes, but bad inputs aren't gdb bugs, so those should be errors
> or warnings, not internal_errors.
for completeness: ... or "complaints", of which the symbol
readers are the biggest users, exactly to complain about
bad input debug info. complaints have the nice property
that they warn once, and go quiet the next time the problem
appears --- when we see a malformed debug info problem, we
tend to see a lot of instances of the same in the same run,
so that feature prevents terminal flooding with a bunch of
duplicated warnings.
--
Pedro Alves
next prev parent reply other threads:[~2011-03-05 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 0:37 Michael Snyder
2011-03-05 0:43 ` Pedro Alves
2011-03-05 0:49 ` Pedro Alves [this message]
2011-03-11 21:35 ` Michael Snyder
2011-03-15 14:44 ` Pedro Alves
2011-03-15 18:07 ` Michael Snyder
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=201103050049.14785.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
/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