From: Jim Blandy <jimb@codesourcery.com>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] stack.c, check return value of lookup_symbol
Date: Mon, 09 Jul 2007 18:01:00 -0000 [thread overview]
Message-ID: <m3vect78y6.fsf@codesourcery.com> (raw)
In-Reply-To: <24208.12.7.175.2.1183748485.squirrel@webmail.sonic.net> (msnyder@sonic.net's message of "Fri, 6 Jul 2007 12:01:25 -0700 (PDT)")
msnyder@sonic.net writes:
>> msnyder@sonic.net writes:
>>> Since it's known that lookup_symbol can return NULL, my first impulse
>>> was to call gdb_assert. That still might be the right thing to do,
>>> since it indicates some sort of internal fault -- but it seems to
>>> me that it isn't necessarily fatal, and simply doing nothing is an
>>> option...
>>
>> gdb_assert calls internal_error, so it's not going to sweep GDB out
>> from under the user. And the situation we're talking about here would
>> be one where we found a symbol in a block, and then looked up that
>> name in that block and didn't find the symbol. I definitely want to
>> see an internal error if that happens.
>
> OK then -- how's this?
That's what I'd do. :)
prev parent reply other threads:[~2007-07-09 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 23:06 msnyder
2007-07-06 15:21 ` Jim Blandy
2007-07-06 19:01 ` msnyder
2007-07-09 18:01 ` Jim Blandy [this message]
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=m3vect78y6.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
/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