From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/4592] access to $bio ioblock.request probe in ioblock.stp fails
Date: Mon, 04 Jun 2007 19:32:00 -0000 [thread overview]
Message-ID: <20070604193231.7386.qmail@sourceware.org> (raw)
In-Reply-To: <20070604192454.4592.wcohen@redhat.com>
------- Additional Comments From fche at redhat dot com 2007-06-04 19:32 -------
(In reply to comment #0)
> When running the systemtap.samples/ioblocktest.stp, the test fails when
> running. It appears to make in invalid access through a pointer.
It would be useful to see the value of the pointer. You can do this by a
modified test case that arranges to print raw $bio and related values.
It could help figure out whether the pointers are invalid, whether the
debugging information is wrong, or something else is amiss.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4592
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-06-04 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 19:25 [Bug tapsets/4592] New: " wcohen at redhat dot com
2007-06-04 19:32 ` fche at redhat dot com [this message]
2007-06-04 20:53 ` [Bug tapsets/4592] " wcohen at redhat dot com
2009-03-23 21:08 ` wcohen 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=20070604193231.7386.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).