This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Recent review of SystemTap test results on ARM running Fedora 15 hard float.


On 02/23/2012 04:55 PM, David Smith wrote:

> On 02/23/2012 04:06 PM, William Cohen wrote:
> 
>> On 02/23/2012 03:54 PM, David Smith wrote:
>>> On 02/23/2012 01:06 PM, William Cohen wrote:
>>
>> Hi David,
>>
>> Thanks for the comments/questions.
>>
>>>
>>>> I reviewed the SystemTap testsuite failures for Fedora 15 hard float running on ARM.  You can see the recent ARM test results in dejazilla at:
>>>>
>>>> http://web.elastic.org/~dejazilla/viewsummary.php?_offset=0&_limit=40&_sort=1A&summary=&age=&rg=&tool=&variant=%3D%27armv7l-unknown-linux-gnu%27&versions=&pass=&fail=&kpass=&kfail=&xpass=&xfail=&untested=&unresolved=&unsupported=&warning=&error=
>>>
>>>


>>>> FAIL: vma_vdsodefault
>>>>       vma_vdso.stp uses uaddr() which didn't work on arm.
>>>
>>>
>>> Hmm, can you tell in systemtap.log what part of 'uaddr()' didn't work?
>>
>> The log wasn't too helpful. When running the test by hand.  Looks like umodename(uaddrr()) == "<unknown>", so getting from
>>
>> 	  printf("%s@%x unknown\n", name, uaddr());
> 
> 
> Hmm, I'll try looking at this one some more.


The first thing we need to do here is figure out which is really
failing, uaddr() or umodname().  Could you change the test to just print
out the return value of uaddr() to see what it is returning?

>>>> FAIL: uprobeslibgcc-O3default-prelink-debug prelink ./libuprobeslibgcc-O3default-prelink-debug.so
>>>> FAIL: uprobeslibgcc-O3default-prelink-sep-debug prelink ./libuprobeslibgcc-O3default-prelink-sep-debug.so
>>>> FAIL: uprobeslibgcc-O3default-prelink-sep-debug-after prelink ./libuprobeslibgcc-O3default-prelink-sep-debug-after.so
>>>>       uprobes not available on arm
>>>
>>>
>>> This is odd.  I would have thought the testsuite would have realized
>>> this platform didn't have uprobes, and not run the test at all.  Which
>>> .exp is this, exelib.exp?
>>
>> Yes, it appears to be running:
>>
>> systemtap.exelib/exelib.exp ...
> 
> Ah, I see what this one is doing now.  I'll bet prelink isn't available
> on arm.  This testcase builds an exe, prelinks it, then does skip the
> actual systemtap tests if !uprobes.
> 
> Is prelink present on your arm system?
> 
> Since prelink isn't present on ia64 either, it might be worthwhile to
> have this testcase check for prelink.


Commit 164901b changes exelib.exp to only run the prelink tests if
prelink exists on the system.  Try the test again and see if it works
better.

-- 

David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]