From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: [PATCH 0/2] Improve error management on probes-based dynamic linker interface (and workaround RH BZ 1196181)
Date: Fri, 21 Aug 2015 23:37:00 -0000 [thread overview]
Message-ID: <1440200253-28603-1-git-send-email-sergiodj@redhat.com> (raw)
Hi,
This series improves the error reporting done by the SystemTap SDT
probe support code, and addresses the problem reported on
<https://bugzilla.redhat.com/show_bug.cgi?id=1196181> by making the
error handling on the probes-based dynamic linker interface more
robust.
Further comments on the patches themselves. I intend to push the
first patch soon if there are no comments.
Thanks,
Sergio.
next reply other threads:[~2015-08-21 23:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 23:37 Sergio Durigan Junior [this message]
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-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
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-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=1440200253-28603-1-git-send-email-sergiodj@redhat.com \
--to=sergiodj@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).