debuginfo path

[Wenji Huang]

Srinivasa DS wrote:
> Wenji Huang wrote:
>> Hi,
>>
>> The commit 921d61030221bc5ff27f8d63d3fa30e93f659484 made the debuginfo 
>> path could be specified with absolute path.
>>
>> But one question, How about relative path, which it will begin with?
> 
> No, one has set SYSTEMTAP_DEBUGINFO_PATH to absolute path, If this env 
> variable is not set, behaviour of systemtap will remain same as before.
> (like searching vmlinux in /boot,/lib/modules/`uname -r` etc).

I means that if we can specify it in relative path,not begin with "/" ? 
For example:

SYSTEMTAP_DEBUGINFO_PATH=build

Seems currently not supported.

> 
>>
>> And the update in debugpath.exp
>>
>> [...]
>>  set test "debugpath-good"
>>
>> -spawn env SYSTEMTAP_DEBUGINFO_PATH=:/usr/lib/debug:build stap -e 
>> "probe kernel.function(\"sys_open\") {}" -p2
>>
>> +set uname [exec /bin/uname -r]
>>
>> +spawn env SYSTEMTAP_DEBUGINFO_PATH=/lib/modules/$uname/build stap -e 
>> "probe kernel.function(\"sys_open\") {}" -p2
>> [...]
>>
>> I think we need to cover the installed kernel-debuginfo case which 
>> will put vmlinux under /usr/lib/debug/lib/modules/`uname -r`/
> 
> As we test these systemtap tests on -rc kernels(self built kernel), I 
> thought it would be good to use  /lib/modules/$uname/build rather than 
> /usr/lib/debug/lib/modules/`uname -r`/(as this dir is not created, when 
> we compile selfbuilt kernel).
> 
> If you have idea on any other path where vmlinux of current compiled 
> kernel can be found, Please let me know.
> 
> Thanks
>  Srinivasa DS
> 
> 
> 
> 
And the path is limited to one, not allowed many separated by ":" like 
before, such as

SYSTEMTAP_DEBUGINFO_PATH=/lib/modules/$uname/build:/usr/lib/debug/lib/modules/$uname/

Anyway, these aren't very important. Just about flexibility.

Regards,
Wenji