This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/15542] New: %( CONFIG_NO_SUCH_VAR == "n" ... %) doesn't evaluate to true
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 28 May 2013 15:55:02 +0000
- Subject: [Bug translator/15542] New: %( CONFIG_NO_SUCH_VAR == "n" ... %) doesn't evaluate to true
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15542
Bug ID: 15542
Summary: %( CONFIG_NO_SUCH_VAR == "n" ... %) doesn't evaluate
to true
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: dsmith at redhat dot com
If you use the '%( CONFIG_FOO ' preprocessor conditional on a CONFIG variable
that doesn't exist, its value doesn't equal to 'n'.
====
# stap -ve '%( CONFIG_NO_SUCH_VAR == "n" %? probe begin { exit() } %)'
Input file '<input>' is empty after preprocessing.
Pass 1: parsed user script and 92 library script(s) using
29176virt/16168res/2556shr/14148data kb, in 200usr/30sys/229real ms.
Pass 1: parse failed. [man error::pass1]
====
Strangely enough, using ' != "y" ' works:
====
# stap -ve '%( CONFIG_NO_SUCH_VAR != "y" %? probe begin { exit() } %)'
Pass 1: parsed user script and 92 library script(s) using
29172virt/16160res/2544shr/14144data kb, in 190usr/50sys/240real ms.
Pass 2: analyzed script: 1 probe(s), 1 function(s), 0 embed(s), 0 global(s)
using 29436virt/16684res/2800shr/14408data kb, in 10usr/0sys/5real ms.
Pass 3: translated to C into
"/tmp/stapY2PUI0/stap_e5865cf2f29bdb61e8371744a0339c71_959_src.c" using
29436virt/17000res/3096shr/14408data kb, in 0usr/0sys/1real ms.
Pass 4: compiled C into "stap_e5865cf2f29bdb61e8371744a0339c71_959.ko" in
2110usr/1080sys/3553real ms.
Pass 5: starting run.
Pass 5: run completed in 20usr/150sys/468real ms.
====
If the CONFIG variable doesn't exist, its value should evaluate to "n".
--
You are receiving this mail because:
You are the assignee for the bug.