From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8620 invoked by alias); 16 May 2012 00:02:46 -0000 Received: (qmail 8589 invoked by uid 9586); 16 May 2012 00:02:45 -0000 Date: Wed, 16 May 2012 00:02:00 -0000 Message-ID: <20120516000245.8578.qmail@sourceware.org> From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, jistone/stapdyn, updated. release-1.7-232-g91101b9 X-Git-Refname: refs/heads/jistone/stapdyn X-Git-Reftype: branch X-Git-Oldrev: 0c26033f4abcbee41fd2278b1c45e4975bddd1ad X-Git-Newrev: 91101b9c2d0f896be6aee7ab97c37b6079f9fe40 Mailing-List: contact systemtap-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-cvs-owner@sourceware.org List-Archive: Reply-To: systemtap@sourceware.org X-SW-Source: 2012-q2/txt/msg00080.txt.bz2 This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, jistone/stapdyn has been updated via 91101b9c2d0f896be6aee7ab97c37b6079f9fe40 (commit) via 002d7a983ee63d44fc302bd3ddbfa35849db2fd0 (commit) from 0c26033f4abcbee41fd2278b1c45e4975bddd1ad (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 91101b9c2d0f896be6aee7ab97c37b6079f9fe40 Author: Josh Stone Date: Tue May 15 16:41:22 2012 -0700 stapdyn: Add semaphore handling to dynsdt To test data-offset handling, this patch fleshes out SDT semaphore support in the dynsdt test program. It actually required a bit of section gymnastics to figure out the raw file offset of the semaphore, mainly because of the padding between the load addresses of the text and data segments. This code appears to work fine tested on a small executable (the heapsort example, modified to gate on the semaphore). For unknown reasons, it doesn't seem to work on the semaphored SDT in libpython. The semaphore address appears to be computed and value incremented correctly, but the instrumentation never fires. The semaphore even appears already incremented with a simultaneous stap -DDEBUG_UPROBES, and that handler does fire on the python function probes. This may be a case of dyninst failing silently, as it does with longjmp SDT, but more investigation is required... commit 002d7a983ee63d44fc302bd3ddbfa35849db2fd0 Author: Josh Stone Date: Tue May 15 16:40:00 2012 -0700 stapdyn: Use the renamed fileOffsetToAddr This is keeping up with dyninst.git master, basically just s/offsetToAddr/fileOffsetToAddr/ ----------------------------------------------------------------------- Summary of changes: stapdyn/dynsdt.cxx | 59 ++++++++++++++++++++++++++++++++++++++++++-------- stapdyn/stapdyn.cxx | 2 +- 2 files changed, 50 insertions(+), 11 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool