From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/16358] build-id difficulties with hand-built kernels
Date: Sat, 21 Dec 2013 16:13:00 -0000 [thread overview]
Message-ID: <bug-16358-6586-EaqG6CyCYf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16358-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16358
--- Comment #2 from Mark Wielaard <mjw at redhat dot com> ---
Pushed:
commit 641a4f62f1f1940540f1202c1e1aa5ce8c508234
Author: Mark Wielaard <mjw@redhat.com>
Date: Sat Dec 21 00:04:21 2013 +0100
libdwfl: Correct nested asprintf result check in report_kernel_archive.
Because of wrongly placed parens the result of only one asprintf call
was checked correctly. Causing dwfl_linux_kernel_report_offline to return
ENOMEM. Rewrite nested if unlikely check into separate if statements to
make clear what is actually being checked and what the actual unlikely
condition is.
Reported against systemtap "build-id difficulties with hand-built kernels"
https://sourceware.org/bugzilla/show_bug.cgi?id=16358
Reported-by: Crestez Dan Leonard <lcrestez@ixiacom.com>
Signed-off-by: Mark Wielaard <mjw@redhat.com>
https://git.fedorahosted.org/cgit/elfutils.git/commit/?id=641a4f62f1f1940540f1202c1e1aa5ce8c508234
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2013-12-21 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 19:10 [Bug translator/16358] New: " fche at redhat dot com
2013-12-20 23:07 ` [Bug translator/16358] " mjw at redhat dot com
2013-12-21 16:13 ` mjw at redhat dot com [this message]
2017-10-11 10:44 ` mark at klomp dot org
2017-10-11 10:48 ` mjw at fedoraproject dot org
2020-10-06 0:19 ` fche at redhat dot com
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=bug-16358-6586-EaqG6CyCYf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).