Solved. The reason I was not able to get the symbols is because logging
has to be enabled, otherwise the symbols are not loaded. In "elfload.c"
there is the condition:
if (qemu_log_enabled()) {
load_symbols(ehdr, image_fd, load_bias);
}
Thanks!
Kind regards,
Rafael
On 5/1/2018 6:28 PM,
Rafael Kioji writes:
> This logging flag prints what I want. But I really wanted is to get
> this info inside the QEMU source code. Why am I not able to lookup the
> symbols in the translator.c file the way I showed?
Without a failing patch it's hard to say, after all the working
disassembly is
On 1 May 2018 at 11:20, Rafael Kioji wrote:
> This logging flag prints what I want. But I really wanted is to get this
> info inside the QEMU source code. Why am I not able to lookup the symbols in
> the translator.c file the way I showed?
The -d in_asm logging is just using lookup_symbol() (eg f
This logging flag prints what I want. But I really wanted is to get this
info inside the QEMU source code. Why am I not able to lookup the
symbols in the translator.c file the way I showed?
Kind regards,
Rafael
On 5/1/2018 6:04 PM, Alex Bennée wrote:
Rafael Kioji writes:
Dear all,
During
Rafael Kioji writes:
> Dear all,
>
> During translation how can I identify what is the basic block of the
> guest code? I wanted to know whether the block being translated is the
> beginning of a function and get its name.
>
> My current approach involves looking up the symbol associated with th
Dear all,
During translation how can I identify what is the basic block of the
guest code? I wanted to know whether the block being translated is the
beginning of a function and get its name.
My current approach involves looking up the symbol associated with the
first PC of the translation b
