| Summary: | stap probes user space markers don't work with 32-on-64 executables | ||
|---|---|---|---|
| Product: | systemtap | Reporter: | Mark Wielaard <mark> |
| Component: | translator | Assignee: | Mark Wielaard <mark> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fche, scox |
| Priority: | P2 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Host: | Target: | ||
| Build: | Last reconfirmed: | ||
| Bug Depends on: | 10601 | ||
| Bug Blocks: | |||
| Attachments: | 10289 test | ||
commit: 54bc8f4243 I don't yet have a test because this fix ends up failing with an unrelated problem: kernel read fault at 0xfffffffffffffe15 (addr) near identifier '$arg1' (In reply to comment #1) > commit: 54bc8f4243 > I don't yet have a test because this fix ends up failing with an unrelated > problem: kernel read fault at 0xfffffffffffffe15 (addr) near identifier '$arg1' Try with "--skip-badvars". Created attachment 4066 [details]
10289 test
With --skip-badvars the probes are found and invoked okay but the local variable values seem to be incorrect. reopen to verify local variable values I suspect this is a duplicate of, or similar to, bug #10318 sdt v3 solves this. |
The exelib.exp tests contain mark.tcl tests that don't work when enabling the (currently disabled) -m32 tests. Running one of these tests by hand gives: $ /usr/local/systemtap/bin/stap -ve 'probe process("./uprobesgcc-O0-m32-debug-uprobeslibgcc-O0-m32-debug_exe").mark("main_count") { printf("main_count: %d\n", $arg1) }' Pass 1: parsed user script and 54 library script(s) in 330usr/20sys/359real ms. semantic error: no match while resolving probe point process("./uprobesgcc-O0-m32-debug-uprobeslibgcc-O0-m32-debug_exe").statement(4252272164411311299) semantic error: no probes found Pass 2: analyzed script: 0 probe(s), 0 function(s), 0 embed(s), 0 global(s) in 10usr/0sys/5real ms. Pass 2: analysis failed. Try again with another '--vp 01' option. Note the large statement value stap derived from the .probes section.