RFC: Disassembly with call frame information
Szabolcs Nagy
szabolcs.nagy@arm.com
Thu Oct 26 14:04:10 GMT 2023
More information about the Binutils mailing list
Thu Oct 26 14:04:10 GMT 2023
- Previous message (by thread): RFC: Disassembly with call frame information
- Next message (by thread): [PATCH] libctf: fix creation-time parent/child dict confusions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
The 10/20/2023 18:25, Hans-Peter Nilsson wrote: > > I am not sure how much information to display. Currently I am just > > showing the CFA assignments, but maybe I need to include the rbp and > > ra updates as well ? > > Sounds like the information would otherwise be incomplete, with > references to those registers but not displaying their values; > initial and as they change. Also, there'd be nice symmetry if > --disassemble-with-cfi has the same information as > --dwarf=frames-interp. Maybe tie the option names better? > Though --disassemble-with-dwarf-frames-interp seems chewy. fwiw i'd do the cmdline like -r vs '-d -r' for relocs: if user asks for both disasm and cfi then display the cfi inline with the asm. or use -d --dwarf=frames-interp-inline. i prefer --dwarf=frames to --dwarf=frames-interp as it is more complete (e.g. target specific pseudo regs are not visible in frames-interp). just interleaving the opcodes with the disasm sounds good enough for me (the opcodes closely match the .cfi directives in asm which users should be familiar with).
- Previous message (by thread): RFC: Disassembly with call frame information
- Next message (by thread): [PATCH] libctf: fix creation-time parent/child dict confusions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list