This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/12947] New: Use of hardware watchpoint causing oops
- From: "wcohen at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 28 Jun 2011 21:03:30 +0000
- Subject: [Bug runtime/12947] New: Use of hardware watchpoint causing oops
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=12947
Summary: Use of hardware watchpoint causing oops
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: wcohen@redhat.com
Created attachment 5825
--> http://sourceware.org/bugzilla/attachment.cgi?id=5825
Serial console of the run with the oops
I was experimenting to the hardware watchpoints.
I had one script that would give me an address of the place going to probe and
then had another another script to initialize the hardware watchpoint and
record backtraces when the memory location was accessed.
Find the address with:
[wcohen@montague tmp]$ stap -g find_free_ram_addr.stp
&global_page_state(NR_FREE_PAGES) = 0xffffffffc0bb0eb0
Then set monitoring with:
[wcohen@montague tmp]$ stap -g track_free_ram.stp 0xc0bb0eb0
Attached is log of the run.
This was using
kernel-2.6.38.8-32.fc15.i686
systemtap-1.5-1.fc15.i686
It seems like that the hw watch points should be better behaved.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.