changes about Call Trace:
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 17 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | makes print_symbol() return intinclude/ kernel/ | +12 | 3 replies | |
| 2/3 | use usual call trace format on x86-64arch/ | +7 | 3 replies | |
| 3/3 | omit symbol size field in print_symbol()kernel/ | +2 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] changes about Call Trace:
Hello,
I realized two things when I was porting my small script oops2line to x86-64. (read call trace, find correspondance modules, calculate addr and addr2line)
If I'm missing something, please let me know.
a) On x86-64 we get different Call Trace format than other architectures when we get oops or press SysRq-t:
<ffffffffa008ef6c>{:jbd:kjournald+1030}
There is a architecture independent function print_symbol(). How about using it on x86-64? But it changes to:
[<ffffffffa008ef6c>] kjournald+0x406/0x578 [jbd]
b) I can't find useful usage for the symbol size in print_symbol(). And symbolsize seems to be fixed when vmlinux or modules are compiled. So we can calculate it from vmlinux or modules.
How about removing the field of symbolsize in print_symbol()?
[<ffffffffa008ef6c>] kjournald+0x406 [jbd]