From: John Snow <jsnow@redhat.com>
To: Claudio Fontana <claudio.fontana@huawei.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Ajo Jose Panoor <ajo.jose.panoor@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] enable-gprof configuration option issue?
Date: Thu, 5 Nov 2015 15:16:09 -0500 [thread overview]
Message-ID: <563BB909.6080507@redhat.com> (raw)
In-Reply-To: <563A360E.3060506@huawei.com>
On 11/04/2015 11:45 AM, Claudio Fontana wrote:
> Hello,
>
> we are trying to use good old gprof to profile the QEMU process,
> and it seems to work when directly passing "-O0 -pg" using --extra-cflags,
> while it does not seem to work when using "--enable-gprof".
>
> The error we get when using --enable-gprof is the following:
>
> ld: gcrt1.o: relocation R_X86_64_32S against `__libc_csu_fini' can not be used when making a shared object; recompile with -fPIC
> gcrt1.o: could not read symbols: Bad value
>
> We got this on a few X86 boxes with different distros, in my case I have Slackware-14.1 64bit, ld 2.23.52.0.1.20130226, gcc 4.8.2
>
> Is the expectation that one should pass "-pg" directly?
>
> Thanks!
>
> Ciao,
>
> Claudio
>
>
It looks like our configure script currently only prepends -p when you
specify --enable-gprof, and not -pg. It doesn't appear to set -O0
either; you probably want --enable-debug --enable-gprof.
I'm not very familiar with gprof or the flags that make the most sense
for it, so it might be in your interest to send a patch over to make
this configure option more useful.
--js
prev parent reply other threads:[~2015-11-05 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 16:45 [Qemu-devel] enable-gprof configuration option issue? Claudio Fontana
2015-11-05 20:16 ` John Snow [this message]
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=563BB909.6080507@redhat.com \
--to=jsnow@redhat.com \
--cc=ajo.jose.panoor@huawei.com \
--cc=claudio.fontana@huawei.com \
--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).