This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: xfer_memory instead of target_read_memory in gdbtk_dis_asm_read_memory


Why is it that
gdbtk_dis_asm_read_memory uses xfer_memory instead of target_read_memory??
I see the documented assumption, but why is that
assumption made?

Performance. Accessing the local executable's text section is faster than a remote target's memory.


However, the assumption has problems. Insight can't disassemble stuff in the BSS section or on the stack.

GDB's gdb_disassemble() function was recent changed to not do this performance tweak, instead ``set trust read-only-sections on'' can be used. Insight should also just use gdb_disassemble().

Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]