public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] libdwfl: dwfl_standard_argp should not fail when not able to attach Dwfl.
Date: Sat, 14 Jun 2014 00:57:46 +0200	[thread overview]
Message-ID: <1402700266.4033.22.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 1402406480-18420-1-git-send-email-mjw@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]

On Tue, 2014-06-10 at 15:21 +0200, Mark Wielaard wrote:
> As pointed out in https://bugzilla.redhat.com/show_bug.cgi?id=1107654
> commit 191080 introduced a thinko that caused dwfl_standard_argp
> to fail if the Dwfl couldn't be attached. Instead of generating a warning
> as the comment intended, the failure would be fatal. But even warning
> about dwfl_core_file_attach () or dwfl_linux_proc_attach () failing
> would be a mistake. The caller/user might not be interested in such
> a non-fatal issue. So just ignore if the call failed for whatever reason.
> If the caller is interested in warning up front about this issue, then
> dwfl_pid () should be called to check the Dwfl is attached. Things should
> work just fine for anything that doesn't call any of the dwfl_state related
> functions.
> 
> Signed-off-by: Mark Wielaard <mjw@redhat.com>
> ---
>  libdwfl/ChangeLog  |    5 +++++
>  libdwfl/argp-std.c |   13 +++++--------
>  2 files changed, 10 insertions(+), 8 deletions(-)

I pushed this patch and the followup "libdwfl: Record dwfl_attach_state
error and return it on failure." patch to master now.

Cheers,

Mark


             reply	other threads:[~2014-06-13 22:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 22:57 Mark Wielaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-10 13:21 Mark Wielaard

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=1402700266.4033.22.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=elfutils-devel@lists.fedorahosted.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).