From: "bugzilla at tecnocode dot co.uk" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15586] Dyninst does not support probefunc()
Date: Thu, 18 Aug 2016 15:54:00 -0000 [thread overview]
Message-ID: <bug-15586-6586-3W1SUWpNnJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15586-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15586
--- Comment #2 from Philip Withnall <bugzilla at tecnocode dot co.uk> ---
(In reply to Philip Withnall from comment #1)
> I suspect this is essentially bug #16795.
Er, I meant bug #14703. Copy–paste error, sorry.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-08-18 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 18:58 [Bug dyninst/15586] New: " swagiaal at redhat dot com
2013-06-05 19:12 ` [Bug dyninst/15586] " jistone at redhat dot com
2016-08-18 15:52 ` bugzilla at tecnocode dot co.uk
2016-08-18 15:54 ` bugzilla at tecnocode dot co.uk [this message]
2016-08-18 16:06 ` jistone at redhat dot com
2020-06-16 21:12 ` scox 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-15586-6586-3W1SUWpNnJ@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).