qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rafael Kioji <rafaelkioji@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Translation block identification.
Date: Tue, 1 May 2018 18:47:13 +0800	[thread overview]
Message-ID: <ee6f3065-2a80-aad9-e835-5be84f2d0bd5@gmail.com> (raw)
In-Reply-To: <CAFEAcA-XVP-z2==XJk265KG8N-3ECVuZ3ubFuVO7O0_RxssBcA@mail.gmail.com>

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, Peter Maydell wrote:
> On 1 May 2018 at 11:20, Rafael Kioji <rafaelkioji@gmail.com> 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 for arm
> I think it's in arm_tr_disas_log() that that particular logging
> is done), so if it works when it's called by the existing QEMU code
> but not in your modification then it sounds like there's an
> error in your modification somewhere.
>
> thanks
> -- PMM

  reply	other threads:[~2018-05-01 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  9:28 [Qemu-devel] Translation block identification Rafael Kioji
2018-05-01 10:04 ` Alex Bennée
2018-05-01 10:20   ` Rafael Kioji
2018-05-01 10:28     ` Peter Maydell
2018-05-01 10:47       ` Rafael Kioji [this message]
2018-05-01 10:43     ` Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee6f3065-2a80-aad9-e835-5be84f2d0bd5@gmail.com \
    --to=rafaelkioji@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).