Testsuite run on ppc64

[William Cohen]

Hien Nguyen wrote:
> William Cohen wrote:
> 
>> Hien Nguyen wrote:
>>
>>> Frank Ch. Eigler wrote:
>>>
>>>> There may be a systemic error in the dejagnu regexps, where multiple
>>>> lines of output are generated by systemtap or the probe, and are
>>>> intended to be matched individually.  The "-re "SOMETHING.*\r"
>>>> idiom may need to become something like "-re SOMETHING[^\r]*\r".
>>>>
>>>> - FChE
>>>>
>>>>  
>>>>
>>> Bingo :-)
>>
>>
>>
>> I just checked in changes based on Franks suggestions. For symbol.exp, 
>> syscall[1,2].exp. Those should provide better results.
>>
>> -Will
>>
> Yes, all tests passed except for the kmodule test . Look under 
> /usr/lib/debug/lib/modules/2.6.9-22.EL, and yes the ext3 debuginfo is 
> there.
> 
> #find . -name "ext3*"
> ./kernel/fs/ext3
> ./kernel/fs/ext3/ext3.ko.debug
> 

Hien,

The revised tests work. Good.

Narrowing down the problem with kmodule.stp. Here is a list of possible 
failure modes and the first one looks likely:

1) The debuginfo information for the module is not correct or not available.
	I see the following error message in the output of "stap -V":

WARNING: cannot find module ext3 debuginfo: No such file or directory

	Check to see that kernel-debuginfo provides "ext3.ko.debug"

	rpm -qs kernel-debuginfo | grep "ext3.ko.debug"

	Does the following list the appropriate symbol(ext3_sync_file)?

nm /usr/lib/debug/lib/modules/`uname -r`/kernel/fs/ext3/ext3.ko.debug


2) Elfutils is not reading the information correctly.
	Which version of elfutils are you using? 0.116?
	x86_64 had problems with modules with earlier elfutils.
	Make sure that you have the elfutils-0.116 installed

3) Translator is missing the symbol. Could this be a symbol naming 
problem, e.g. compiler for ppc64 generates different labels.


-Will