From: "sapatel at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug bpf/24946] printing hex sequences causes crash
Date: Tue, 03 Sep 2019 20:10:00 -0000 [thread overview]
Message-ID: <bug-24946-6586-PP3wAeh9wf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24946-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24946
--- Comment #3 from Sagar Patel <sapatel at redhat dot com> ---
(In reply to Sagar Patel from comment #2)
> Fixed in commit 728bbc1ac.
>
> This is a temporary patch, and will be reverted after PR13371 is fixed.
The portion of the patch dealing with this PR will not be reverted, only the
portion dealing with PR24947 will be reverted.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2019-09-03 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 21:30 [Bug bpf/24946] New: " sapatel at redhat dot com
2019-08-30 20:20 ` [Bug bpf/24946] " sapatel at redhat dot com
2019-09-03 20:08 ` sapatel at redhat dot com
2019-09-03 20:10 ` sapatel at redhat dot com [this message]
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-24946-6586-PP3wAeh9wf@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).