| Summary: | [2.6 M4 RC1] [OE-Core] Crosstap doesn't work on 2.6 M4 RC1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | pankaj yadav <pankaj-y> | ||||
| Component: | configuration | Assignee: | Victor Kamensky <victor.kamensky7> | ||||
| Status: | RESOLVED INVALID | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | Medium | CC: | ee.peng.yeoh | ||||
| 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
pankaj yadav
2018-11-01 07:21:20 UTC
Same issue has been observed with yocto-2.7_M1.rc1 QA execution. Hi Pankaj,
Appreciate SystemTap and crosstap testing. But the issue
you observe is not a bug. SystemTap and crosstap are working
as they supposed to: script got compiled and module is
activated. The reason why you don't see any output from such
script is because nothing in the system makes 'open'
system call, so script does not report anything. It was
a change in glibc that instead of 'open' system call 'openat'
actually used on all platforms as glibc 'open' function
implementation. So if you change your SystemTap
script to trace 'openat' system call instead of tracing
'open' system call you will see desired results:
[kamensky@kamensky-w530 build]$ cat trace_openat.stp
probe syscall.openat
{
printf ("%s(%d) openat (%s)\n", execname(), pid(), argstr)
}
[kamensky@kamensky-w530 build]$ crosstap root@192.168.7.2 trace_openat.stp
ls(384) openat (AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC)
ls(384) openat (AT_FDCWD, "/lib/libm.so.6", O_RDONLY|O_CLOEXEC)
ls(384) openat (AT_FDCWD, "/lib/libresolv.so.2", O_RDONLY|O_CLOEXEC)
ls(384) openat (AT_FDCWD, "/lib/libc.so.6", O_RDONLY|O_CLOEXEC)
ls(384) openat (AT_FDCWD, ".", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC)
You can double check that nothing calls 'open' system call
with strace. Add it to the image and try to trace few apps -
you will see that only 'openat' system call will be issued.
For example, tracing 'cat' command:
root@qemux86-64:~# touch foo
root@qemux86-64:~# strace -o /tmp/cat.trace.txt cat foo
root@qemux86-64:~# grep open /tmp/cat.trace.txt
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/libm.so.6", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/libresolv.so.2", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
openat(AT_FDCWD, "foo", O_RDONLY) = 3
root@qemux86-64:~#
I will put this PR into RESOLVED state with INVALID resolution (it
seems correct state/resolution for non-bugs). If you disagree please
move it back to NEW with proper explanation.
Thanks,
Victor
|