From: "Andrew Burgess" <aburgess@broadcom.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] New OPTIMIZED_OUT_ERROR error code.
Date: Mon, 02 Dec 2013 13:53:00 -0000 [thread overview]
Message-ID: <529C9055.1020201@broadcom.com> (raw)
In-Reply-To: <1385756149-534-2-git-send-email-palves@redhat.com>
On 29/11/2013 8:15 PM, Pedro Alves wrote:
> In order to catch <optimized out> errors like we catch <unavailable>
> errors, this adds a new OPTIMIZED_OUT_ERROR error code, and throws it
> in various places.
>
> gdb/ChangeLog
> 2013-11-29 Andrew Burgess <aburgess@broadcom.com>
> Pedro Alves <palves@redhat.com>
>
> * exceptions.h (errors): Add OPTIMIZED_OUT_ERROR.
> * dwarf2loc.c (write_pieced_value): Throw OPTIMIZED_OUT_ERROR.
> * frame.c (frame_unwind_register): Throw OPTIMIZED_OUT_ERROR.
> * spu-tdep.c (spu_software_single_step): Throw
> OPTIMIZED_OUT_ERROR.
> * valops.c (value_assign): Throw OPTIMIZED_OUT_ERROR.
For what it's worth; looks good to me :)
Thanks,
Andrew
next prev parent reply other threads:[~2013-12-02 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:16 [PATCH 0/2] Fix "info frame" in the outermost frame Pedro Alves
2013-11-29 20:20 ` [PATCH 2/2] " Pedro Alves
2013-12-02 9:04 ` Yao Qi
2013-12-02 10:05 ` Pedro Alves
[not found] ` <52A3DBA6.6060706@codesourcery.com>
2013-12-09 10:58 ` Pedro Alves
2013-11-29 20:39 ` [PATCH 1/2] New OPTIMIZED_OUT_ERROR error code Pedro Alves
2013-12-02 13:53 ` Andrew Burgess [this message]
2013-12-06 20:01 ` [PATCH 0/2] Fix "info frame" in the outermost frame 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=529C9055.1020201@broadcom.com \
--to=aburgess@broadcom.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