From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14028 invoked by alias); 12 Sep 2012 21:21:38 -0000 Received: (qmail 14013 invoked by uid 22791); 12 Sep 2012 21:21:36 -0000 X-SWARE-Spam-Status: No, hits=-3.1 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Sep 2012 21:21:24 +0000 From: "jistone at redhat dot com" To: systemtap@sourceware.org Subject: [Bug dyninst/14573] New: Pass pt_regs to dyninst probe handlers Date: Wed, 12 Sep 2012 21:21:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: dyninst X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jistone at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2012-q3/txt/msg00300.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14573 Bug #: 14573 Summary: Pass pt_regs to dyninst probe handlers Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: dyninst AssignedTo: systemtap@sourceware.org ReportedBy: jistone@redhat.com Classification: Unclassified In order to examine much process state with stapdyn, we're going to need registers. We should pass a pt_regs* (/usr/include/asm/ptrace.h) as a parameter to the probe handler. I believe this can be allocated and prepared via BPatch_register code snippets. We will probably need to hardcode architecture-specific support for the register layouts, but I think that's ok as these are generally unchanging. Not all registers will be available. Right now dyninst only exposes the general purpose registers, and none of the special registers. We do need access to the frame and stack pointers, but that should come soon - see: https://lists.cs.wisc.edu/archive/dyninst-api/2012/msg00093.shtml -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.