From: "tschan+sourceware at devzone dot ch" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/14774] process.statement("*@file:*") probes don't match all functions
Date: Tue, 30 Oct 2012 11:52:00 -0000 [thread overview]
Message-ID: <bug-14774-6586-O0fv6VKmXZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14774-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14774
--- Comment #6 from Daniel Tschan <tschan+sourceware at devzone dot ch> 2012-10-30 11:51:54 UTC ---
Created attachment 6709
--> http://sourceware.org/bugzilla/attachment.cgi?id=6709
Differences of test suite runs before and after patch.
Thank you for committing the patch. Test case to follow.
Turns out that I have to run the test suite as root, otherwise the semko.exp
test case runs indefinitely, or rather till the system runs out of memory. Now
after the complete test suite ran through I see some differences before and
after my fix. There are 4 fewer unexpected failures, see attached diff.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-10-30 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 15:14 [Bug uprobes/14774] New: " tschan+sourceware at devzone dot ch
2012-10-27 16:11 ` [Bug uprobes/14774] " tschan+sourceware at devzone dot ch
2012-10-27 16:22 ` [Bug translator/14774] " fche at redhat dot com
2012-10-27 22:38 ` tschan+sourceware at devzone dot ch
2012-10-27 23:38 ` fche at redhat dot com
2012-10-29 20:01 ` fche at redhat dot com
2012-10-30 11:52 ` tschan+sourceware at devzone dot ch [this message]
2012-10-30 15:08 ` fche at redhat dot com
2012-11-03 19:19 ` tschan+sourceware at devzone dot ch
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-14774-6586-O0fv6VKmXZ@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).