>> index 1d915b1..f4334ac 100755
>> --- a/x86_64.c
>> +++ b/x86_64.c
>> @@ -5389,7 +5389,7 @@ search_for_switch_to(ulong start, ulong end)
>> found = FALSE;
>> sprintf(buf1, "x/%ldi 0x%lx", max_instructions, start);
>> if (symbol_exists("__switch_to"))
>> - sprintf(buf2, "callq 0x%lx", symbol_value("__switch_to"));
>> + sprintf(buf2, "call 0x%lx", symbol_value("__switch_to"));
>
> I don't know why you see it with a "call" instruction? On all x86_64 kernels
> I've seen, it looks like this:
>
> crash> dis __schedule
> ... [ cut ] ...
> 0xffffffff81659c81 <__schedule+657>: callq 0xffffffff81013450 <__switch_to>
> ...
>
> Maybe we can search for both strings?
>
crash> dis context_switch
0xffffffff80278af4 <context_switch+596>: call
0xffffffff80205600 <__switch_to>
I have no explanation for the difference. I will submit another
version that searches for both strings.
> Dave
>
>
> --
> Crash-utility mailing list
> Crash-utility@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/crash-utility
--
Crash-utility mailing list
Crash-utility@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/crash-utility
