From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5294 invoked by alias); 31 Oct 2009 15:46:13 -0000 Received: (qmail 5224 invoked by uid 48); 31 Oct 2009 15:46:01 -0000 Date: Sat, 31 Oct 2009 15:46:00 -0000 From: "fche at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20091031154558.10877.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/10877] New: improve probe point error reporting 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/msg00379.txt.bz2 Currently we store just one tok* per probe_point, instead of one per probe point element (the stuff around the dots). This leads to hard-to-interpret error messages % stap -p2 -e 'probe kernel.junkction("sdf") {}' semantic error: probe point mismatch at position 1 (alternatives: function(number) function(string) mark(string) statement(number) statement(string) trace(string)): identifier 'kernel' at :1:7 while resolving probe point kernel.junkction("sdf") source: probe kernel.junkction("sdf") {} ^ Pass 2: analysis failed. Try again with another '--vp 01' option. Instead, we should store a tok* per probe point element, so that an error can point the caret at just the right spot, and we can drop the "at position N" from the error description body. -- Summary: improve probe point error reporting Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: translator AssignedTo: systemtap at sources dot redhat dot com ReportedBy: fche at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=10877 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.