From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11726 invoked by alias); 18 Jul 2012 22:22:02 -0000 Received: (qmail 11711 invoked by uid 22791); 18 Jul 2012 22:22:01 -0000 X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 18 Jul 2012 22:21:48 +0000 From: "jistone at redhat dot com" To: systemtap@sourceware.org Subject: [Bug translator/14369] Markers with $vars are reported "not found" when missing debuginfo Date: Wed, 18 Jul 2012 22:22:00 -0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: translator X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jistone at redhat dot com X-Bugzilla-Status: WAITING X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Status Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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: 2012-q3/txt/msg00051.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14369 Josh Stone changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING --- Comment #1 from Josh Stone 2012-07-18 22:21:47 UTC --- (In reply to comment #0) > We ought to fall back on this direct method when the query_addr path fails, and > then the $foo can fail later (if it even survives optimization). commit 73d53dd2213ce54a72db9b3bd029eb1f39760656 With this, we now get: > $ gcc ../testsuite/systemtap.base/sdt_asm.S -o sdt_asm.x > $ ./run-stap -e 'probe process("./sdt_asm.x").mark("*") { println($foo) }' -p2 > WARNING: cannot find module /home/jistone/systemtap/build/sdt_asm.x debuginfo: No DWARF information found > semantic error: target-symbol requires debuginfo: identifier '$foo' at :1:50 > source: probe process("./sdt_asm.x").mark("*") { println($foo) } > ^ > > Pass 2: analysis failed. Try again with another '--vp 01' option. > $ gcc ../testsuite/systemtap.base/sdt_asm.S -o sdt_asm.x -g > $ ./run-stap -e 'probe process("./sdt_asm.x").mark("*") { println($foo) }' -p2 > semantic error: target-symbol requires debuginfo: identifier '$foo' at :1:50 > source: probe process("./sdt_asm.x").mark("*") { println($foo) } > ^ > > Pass 2: analysis failed. Try again with another '--vp 01' option. > $ ./run-stap -e 'probe process("./sdt_asm.x").mark("*") { println(@defined($foo)) }' -p2 > # probes > process("/home/jistone/systemtap/build/sdt_asm.x").statement(0x4004ab) /* pc=.absolute+0x4ab */ /* <- process("./sdt_asm.x").mark("memory") = process("./sdt_asm.x").statement(0x4004ab) <- process("./sdt_asm.x").mark("*") */ > process("/home/jistone/systemtap/build/sdt_asm.x").statement(0x4004b1) /* pc=.absolute+0x4b1 */ /* <- process("./sdt_asm.x").mark("a") = process("./sdt_asm.x").statement(0x4004b1) <- process("./sdt_asm.x").mark("*") */ I'm not entirely thrilled with how the new error gets chained though, when full debuginfo is present: > $ ./run-stap -e 'probe process("./stap").mark("*") { println($foo) }' -p2 > semantic error: unable to find local 'foo' near pc 0x41140f in cleanup ../main.cxx ( (alternatives: $s $rc): identifier '$foo' at :1:45 > source: probe process("./stap").mark("*") { println($foo) } > ^ > > semantic error: target-symbol requires debuginfo: identifier '$foo' at :1:45 > source: probe process("./stap").mark("*") { println($foo) } > ^ > > Pass 2: analysis failed. Try again with another '--vp 01' option. Ideas on how to improve that are welcome... -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.