Bug 12950

Summary: [Yocto-2.6_M3.rc1] [MANUAL_SCRIPTS_OE-Core] [Case 2021] [Cross_tap]semantic error: while resolving probe point: identifier 'syscall' at trace_open.stp
Product: [Build System, Metadata & Runtime] OE-Core Reporter: pankaj yadav <pankaj-y>
Component: configurationAssignee: Victor Kamensky <victor.kamensky7>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, richard.purdie, victor.kamensky7
Version: 2.6   
Target Milestone: 2.7   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
Screenshot for Cropstap issue observed in 2.6M3RC1 none

Description pankaj yadav 2018-10-04 05:27:05 UTC
Created attachment 4374 [details]
Screenshot for Cropstap issue observed in 2.6M3RC1

Issue has been observed with 2.6M3RC1 release.
Regression : Issue is not reproducible with 2.6M2RC1 release


Steps to reproduce :
Step 1: Create the trace_open.stp script as follows in the host machine: 
probe syscall.open

{ printf ("%s(%d) open (%s)\n", execname(), pid(), argstr) }
if the above failed, then create the below instead.
probe syscall.open

{ printf ("%s(%d) open\n", execname(), pid()) }
Step 2: Add 'tools-profile' and 'ssh-server-openssh' to EXTRA_IMAGE_FEATURES in local.conf
Step 3: Build a core-image-minimal image, build systemtap-native. Start the image under qemu.
Step 4: Make sure that the ssh service is started on the Qemu machine.
Step 5: From the host machine poky build_dir, run "crosstap root@192.168.7.2 trace_open.stp".


Logs for 2.6M3RC1:
pankajsx@andromeda02:/data/pankajsx/2.6M3RC1/poky_crosstap/poky/build$ crosstap root@192.168.7.2 trace_open.stp
semantic error: while resolving probe point: identifier 'syscall' at trace_open.stp:1:7
source: probe syscall.open

Screenshots are attached for the reference.
^
semantic error: no match
Pass 2: analysis failed. [man error::pass2]
pankajsx@andromeda02:/data/pankajsx/2.6M3RC1/poky_crosstap/poky/build$
Comment 1 Victor Kamensky 2018-10-15 05:31:58 UTC
This issue is only observed on x86_64 target. I've checked
all other CPU types the test case works OK there. The issue
happens after OE project moved to 4.18 kernel. It turns
out SystemTap all system call traces in SystemTap 3.3 on
x86_64 do not work on kernels 4.17+. Please look at

https://bugzilla.redhat.com/show_bug.cgi?id=1596456

Unfortunately, there is no reasonable size fix that
could be backported into 3.3. SystemTap just anounced
new 4.0 release and one of major updates there is
[REDHAT #1596456] fix.

I will post systemtap OE recipe update to 4.0 version
shortly, but I am not sure whether it would be accepted
for 2.6.

Note one can workaround issue by using kernel function
traces with proper names directly. I.e like
__x86_sys_open, __ia32_compat_sys_open.

Also note even if issue would be fixed, and SystemTap
module will compile, in OE system at this point not
much code uses open system call, so you would not see
any traces from it. Instead try openat (which currently
is subject to the same issue).
Comment 2 Victor Kamensky 2018-10-15 18:56:08 UTC
Proposed fix by move to SystemTap 4.0 is at
http://lists.openembedded.org/pipermail/openembedded-core/2018-October/156731.html
Comment 3 Richard Purdie 2018-10-18 12:43:28 UTC
Fix was merged: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5a0e22ebc93ed895f7b2cb3faab58c35dbab3e43
Thanks for the help with this Victor!