From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Catching errors on probes-based dynamic linker interface
Date: Wed, 02 Sep 2015 04:22:00 -0000 [thread overview]
Message-ID: <87pp215u3f.fsf@redhat.com> (raw)
In-Reply-To: <8737yx78u5.fsf@redhat.com> (Sergio Durigan Junior's message of "Wed, 02 Sep 2015 00:18:10 -0400")
On Wednesday, September 02 2015, I wrote:
> On Tuesday, September 01 2015, I wrote:
>
>>> I am ok with doing this:
>>>
>>> TRY
>>> {
>>> probe_argc = get_probe_argument_count (pa->probe, frame);
>>> }
>>> CATCH (ex, RETURN_MASK_ERROR)
>>> {
>>> exception_print (gdb_stderr, ex);
>>> probe_argc = 0;
>>> }
>>> END_CATCH
>>>
>>> If you put a big fat comment above the following block, e.g.:
>>>
>>> /* Note that failure of get_probe_argument_count will
>>> set probe_argc == 0. This must result in returning
>>> action = PROBES_INTERFACE_FAILED. */
>>> if (probe_argc == 2)
>>> action = FULL_RELOAD;
>>> else if (probe_argc < 2)
>>> action = PROBES_INTERFACE_FAILED;
>>
>> Great, that works for me as well. I will update the patch here to
>> address this.
>
> I took the liberty to modify and expand the comment; I hope you still
> find it OK. Here's what I pushed.
Pushed.
https://sourceware.org/ml/gdb-cvs/2015-09/msg00002.html
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-09-02 4:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 23:37 [PATCH 0/2] Improve error management on probes-based dynamic linker interface (and workaround RH BZ 1196181) Sergio Durigan Junior
2015-08-21 23:37 ` [PATCH 2/2] Catching errors on probes-based dynamic linker interface Sergio Durigan Junior
2015-08-24 8:43 ` Gary Benson
2015-08-24 16:09 ` Sergio Durigan Junior
2015-08-25 12:47 ` Gary Benson
2015-08-25 18:17 ` Sergio Durigan Junior
2015-09-01 3:27 ` Sergio Durigan Junior
2015-09-01 9:24 ` Gary Benson
2015-09-01 16:26 ` Sergio Durigan Junior
2015-09-02 4:18 ` Sergio Durigan Junior
2015-09-02 4:22 ` Sergio Durigan Junior [this message]
2015-09-02 4:38 ` [PATCH] Initialize variable and silence GCC warning from last commit Sergio Durigan Junior
2015-09-02 4:50 ` [PATCH] Initialize yet another variable to silence GCC warning from last-but-one commit Sergio Durigan Junior
2015-08-21 23:37 ` [PATCH 1/2] Improve error reporting when handling SystemTap SDT probes Sergio Durigan Junior
2015-09-02 4:20 ` Sergio Durigan Junior
2015-09-02 4:20 ` [PATCH 0/2] Improve error management on probes-based dynamic linker interface (and workaround RH BZ 1196181) Sergio Durigan Junior
2015-09-02 16:38 ` Gary Benson
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=87pp215u3f.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gbenson@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).