From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21585 invoked by alias); 21 Feb 2009 16:13:45 -0000 Received: (qmail 21561 invoked by uid 48); 21 Feb 2009 16:13:30 -0000 Date: Mon, 23 Feb 2009 09:47:00 -0000 Message-ID: <20090221161330.21560.qmail@sourceware.org> From: "ananth at in dot ibm dot com" To: systemtap@sources.redhat.com In-Reply-To: <20090220112441.9876.ananth@in.ibm.com> References: <20090220112441.9876.ananth@in.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug tapsets/9876] Syscall tapset broken on architectures that use SYSCALL_WRAPPERS 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-q1/txt/msg00492.txt.bz2 ------- Additional Comments From ananth at in dot ibm dot com 2009-02-21 16:13 ------- The other complex case is when a specific config may cause one or more syscalls to not exist in the kernel eg., sys_kexec_load, currently handled with a ? With the ! construct, how do we prevent a hard failure when the call is absent? -- http://sourceware.org/bugzilla/show_bug.cgi?id=9876 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.