In the calltrace, does anyone know what the numbers after the + mean (see below)? For example, after __handle_sysrq is 0×58/0xc6. Is this some sort of offset into the function where the call was made? I need to pinpoint an exception in a lengthy function. Thanks in advance.
x represents the approx offset into the function . y represents the approx total length of that function. Actually, y is the distance to the next global symbol. Therefore, these are approximations and not exact – but they do give you a “good enough” idea of where the faulting code lies. Typically, you could now try using objdump to disassemble and look at the offsets that show up, matching to the closest ‘x’ offset above.
Manish Sarori says: November 25th, 2008 at 10:20 pmIn the calltrace, does anyone know what the numbers after the + mean (see below)? For example, after __handle_sysrq is 0×58/0xc6. Is this some so
599
到【灌水乐园】发言
November 25th, 2008 at 10:20 pm
In the calltrace, does anyone know what the numbers after the + mean (see below)? For example, after __handle_sysrq is 0×58/0xc6. Is this some sort of offset into the function where the call was made? I need to pinpoint an exception in a lengthy function. Thanks in advance.
Call Trace:
[] __handle_sysrq+0×58/0xc6
[] write_sysrq_trigger+0×23/0×29
December 3rd, 2008 at 9:50 pm
Manish, reg:
+x/y
x represents the approx offset into the function .
y represents the approx total length of that function. Actually, y is the distance to the next global symbol. Therefore, these are approximations and not exact – but they do give you a “good enough” idea of where the faulting code lies. Typically, you could now try using objdump to disassemble and look at the offsets that show up, matching to the closest ‘x’ offset above.