Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org,  asmundak@google.com
Subject: Re: [PATCH v2] Add Guile frame unwinder interface
Date: Mon, 09 Mar 2015 18:54:00 -0000	[thread overview]
Message-ID: <87pp8iq9wc.fsf@igalia.com> (raw)
In-Reply-To: <54FDBF21.4090400@redhat.com> (Pedro Alves's message of "Mon, 09	Mar 2015 15:41:21 +0000")

Hi,

On Mon 09 Mar 2015 16:41, Pedro Alves <palves@redhat.com> writes:

> On 03/09/2015 10:34 AM, Andy Wingo wrote:
>> +@var{register} names a register, and should be a string, for example
>> +@samp{rip}.  @var{value} is the register value, as a @value{GDBN}
>> +value.  Alternately, passing @code{#f} as the value will mark the
>> +register as unavailable.
>
> From a glimpse over the code, I think this actually marks it as
> "<not saved>" (optimized out), right?  That would be the correct
> thing to do.  Marking a register as "<unavailable>" is also possible,
> but it is a different thing -- it means the value exists, but gdb
> couln't get to it, because e.g., the core file is trimmed, or the
> ptrace interface is missing access to some registers.
>
> That said, you may want to consider how you'd expand the API
> to allow marking registers as unavailable.

I didn't realize that "unavailable" and "not saved" were different
things, thanks for the pointer.  I guess given that the default is a
"not saved" result, I can just document this default state, and that
ephemeral-frame-add-saved-value! adds a value.  We remove the #f case.

If we need to support other states like "unavailable", we can add other
API like ephemeral-frame-mark-unavailable! or similar.

>> +  is_unwinding = 1;
>>    TRY_CATCH (ex, RETURN_MASK_ERROR)
>>      {
>>        res = unwinder->sniffer (unwinder, this_frame, this_cache);
>>      }
>> +  is_unwinding = 0;
>
> Note that RETURN_MASK_ERROR does not catch all exceptions (notably,
> a ctrl-c/QUIT passes right through uncaught).

Ah indeed.  I'll move the is_unwinding=1 to a cleanup inside the TRY_CATCH.

Thanks for the review,

Andy


  parent reply	other threads:[~2015-03-09 18:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 15:58 [PATCH] " Andy Wingo
2015-03-09 10:34 ` [PATCH v2] " Andy Wingo
2015-03-09 15:42   ` Pedro Alves
2015-03-09 16:22     ` Eli Zaretskii
2015-03-09 18:54     ` Andy Wingo [this message]
2015-03-10  9:03       ` [PATCH v3] " Andy Wingo
2015-03-10 17:48         ` Doug Evans
2015-03-11  9:33           ` Andy Wingo
2015-03-10 15:46       ` [PATCH v2] " Pedro Alves

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=87pp8iq9wc.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=asmundak@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.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