(2013/12/04 0:15), David Ahern wrote:
> On 12/2/13, 10:12 PM, Masami Hiramatsu wrote:
>>> That needs to be explicitly stated in the error message -- only global
>>> symbols may be given.
>>
>> Ah, I see. In that case, I think the "variable" is not a correct word,
>> the "symbol" is better, because
On 12/2/13, 10:12 PM, Masami Hiramatsu wrote:
>> That needs to be explicitly stated in the error message -- only global
>> symbols may be given.
>
> Ah, I see. In that case, I think the "variable" is not a correct word,
> the "symbol" is better, because perf probe can take tracing variable
> argum
(2013/12/02 23:52), David Ahern wrote:
> On 12/1/13, 10:59 PM, Masami Hiramatsu wrote:
>> (2013/12/02 9:07), David Ahern wrote:
>>> When requesting a function from a userspace library the error message to
>>> the user is less than helpful. e.g.,
>>>
>>> perf probe -x /lib64/libpthread-2.14.90.
On 12/1/13, 10:59 PM, Masami Hiramatsu wrote:
> (2013/12/02 9:07), David Ahern wrote:
>> When requesting a function from a userspace library the error message to
>> the user is less than helpful. e.g.,
>>
>> perf probe -x /lib64/libpthread-2.14.90.so -a
>> 'lock_full=__pthread_mutex_lock_full
(2013/12/02 9:07), David Ahern wrote:
> When requesting a function from a userspace library the error message to
> the user is less than helpful. e.g.,
>
> perf probe -x /lib64/libpthread-2.14.90.so -a
> 'lock_full=__pthread_mutex_lock_full'
> no symbols found in /lib64/libpthread-2.14.90
When requesting a function from a userspace library the error message to
the user is less than helpful. e.g.,
perf probe -x /lib64/libpthread-2.14.90.so -a
'lock_full=__pthread_mutex_lock_full'
no symbols found in /lib64/libpthread-2.14.90.so, maybe install a debug
package?
Failed to
6 matches
Mail list logo
