From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug dyninst/15052] externalvar.exp fails with dyninst
Date: Fri, 08 Jan 2021 20:48:13 +0000 [thread overview]
Message-ID: <bug-15052-6586-WjPYp3NUy7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15052-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15052
Stan Cox <scox at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |scox at redhat dot com
Resolution|--- |NOTABUG
--- Comment #3 from Stan Cox <scox at redhat dot com> ---
Date: Fri Jan 8 15:38:42 2021 -0500
Add stapdyn VMA-tracking.
Added VMA-tracking to stapdyn. externalvar.exp now passes except for the bug
14490 cases.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-01-08 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 20:05 [Bug dyninst/15052] New: " dsmith at redhat dot com
2013-01-23 0:42 ` [Bug dyninst/15052] " jistone at redhat dot com
2013-08-05 18:07 ` dsmith at redhat dot com
2021-01-08 20:48 ` scox 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-15052-6586-WjPYp3NUy7@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).