Re: arm64 kprobes/systemtap support progress

[William Cohen <wcohen at redhat dot com>]

On 11/20/2014 05:56 PM, David Smith wrote:
> On 11/20/2014 10:14 AM, William Cohen wrote:
>> I did a quick look over of the current results and categorized most of
>> them below.
> 
> ... stuff deleted ...
> 
>> Uprobes support not available:
>>
>> FAIL: bad-code
> 
> The above doesn't need uprobes, but it does to a user backtrace. (Or
> does a user backtrace require uprobes?)

Hi David,

For the bad-code it doesn't seem to use the uproces, but it gave message about user-space process-tracking facilities not being available:

Running ./systemtap.base/bad-code.exp ...
Executing on host: gcc ./systemtap.base/bad-code.c  -g  -lm   -o bad-code    (timeout = 300)
spawn -ignore SIGHUP gcc ./systemtap.base/bad-code.c -g -lm -o bad-code

PASS: bad-code.c compile
Running: stap ./systemtap.base/bad-code.stp -w -d ./bad-code -c ./bad-code
spawn stap ./systemtap.base/bad-code.stp -w -d ./bad-code -c ./bad-code

user-space process-tracking facilities not available [man error::process-tracking]

Pass 4: compilation failed.  [man error::pass4]

Executing: kill -INT -4863
main: 0, func: 0, libc: 0
FAIL: bad-code

Thanks for adding the fixes for the ones below.  I also added some fixes to address the syscall remappings for the syscall tests.  It looks like the failures might be less than 100 now.

-Will


> 
>> FAIL: callee (simple - probing .callee(foo))
>> FAIL: callee (multicalls - probing main .callees)
>> FAIL: callee (inlined - probing main .callees)
>> FAIL: callee (extern - probing main .callees)
>> FAIL: callee (reloc - probing shlib foo .callees)
>> FAIL: pr16719 (user - can't start stap)
>> FAIL: sdt_misc wildcard (0) V1_uprobe
>> FAIL: sdt_misc wildcard (0) V2_uprobe
>> FAIL: sdt_misc wildcard (0) V3_uprobe
>> FAIL: stmt_inlines (probing error, expected 4, got 0)
>> FAIL: stmt_rel (bio_init sanity check)
>> FAIL: ./systemtap.examples/general/py2example build
>> FAIL: ./systemtap.examples/memory/last_100_frees build
> 
> I fixed all the above by adding 'uprobes_p' checks to the test cases.
> 
>> FAIL: 64_BIT_UTRACE_SYSCALL_ARGS shutdown (eof)
> 
> The above one isn't a uprobes problem. That test only uses utrace, not
> uprobes (it passes on ia64 for instance, which has utrace but not uprobes).
> 
>> plt support not impletement:
>>
>> FAIL: listing_mode (untested probe type: process(number).plt)
>> FAIL: listing_mode (untested probe type: process(number).plt.return)
>> FAIL: listing_mode (untested probe type: process(number).plt(string))
>> FAIL: listing_mode (untested probe type: process(number).plt(string).return)
> 
> I've fixed these, you should get KFAILs now.
>