From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12318 invoked by alias); 27 Oct 2009 18:40:29 -0000 Received: (qmail 11721 invoked by uid 48); 27 Oct 2009 18:40:13 -0000 Date: Tue, 27 Oct 2009 18:40:00 -0000 Message-ID: <20091027184013.11720.qmail@sourceware.org> From: "roland at gnu dot org" To: systemtap@sources.redhat.com In-Reply-To: <20091023162529.10836.fche@redhat.com> References: <20091023162529.10836.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug uprobes/10836] uprobes-provided pt_regs* are unreliable X-Bugzilla-Reason: AssignedTo 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: 2009-q4/txt/msg00304.txt.bz2 ------- Additional Comments From roland at gnu dot org 2009-10-27 18:40 ------- "synthesized pt_regs" is a loony concept considered only by systemtap. It has no place in the general utrace world. user_regset is there, it's what should be used. The only reason pt_regs is passed into some callbacks is because the pointer is handy and in some circumstances a few of its fields might be sufficiently useful for particular code that knows exactly what it is looking at. General-case code can use the asm/syscall.h macros on it, for example. For any generalized register access, user_regset is the only right thing to use. -- http://sourceware.org/bugzilla/show_bug.cgi?id=10836 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.