From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16379 invoked by alias); 29 Oct 2009 14:29:32 -0000 Received: (qmail 14850 invoked by uid 48); 29 Oct 2009 14:29:11 -0000 Date: Thu, 29 Oct 2009 14:29:00 -0000 Message-ID: <20091029142911.14849.qmail@sourceware.org> From: "fche at redhat dot com" 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/msg00351.txt.bz2 ------- Additional Comments From fche at redhat dot com 2009-10-29 14:29 ------- (In reply to comment #10) > What are the main registers one needs to know here? In the context of uprobes, apprx. all of them, since they may contain $variable addresses / values. > Helpers like regset_instruction_pointer(task), regset_stack_pointer(task) > would be a useful addition with or without uprobes [...] While I've been thinking about this mainly for uprobes, we get related complications from utrace & timer.profile type probes, if someone were to invoke print_ubacktrace(). -- 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.