From: "Leonardo E. Reiter" <lreiter@win4lin.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] glibc abort if -snapshot is used
Date: Wed, 23 Aug 2006 12:48:23 -0400 [thread overview]
Message-ID: <44EC86D7.60008@win4lin.com> (raw)
In-Reply-To: <1156349642.28280.2.camel@r51.oakcourt.dyndns.org>
FYI... you can actually run the unstripped binaries from the build tree
instead of the target installation directory. For example, if you have
qemu installed in /opt/qemu, but you built in
/home/andrew/packages/src/qemu, instead of:
/opt/qemu/bin/qemu
run:
/home/andrew/packages/src/qemu/i386-softmmu/qemu
replace i386-softmmu with whatever target you are trying to run if
that's not it. The binary is not stripped until after it's installed in
the target directory, so you can use the one in the build directory for
debugging if needed.
- Leo Reiter
Andrew Barr wrote:
> On Tue, 2006-08-22 at 22:40 -0500, Rene Horn wrote:
>> Why not just build it right from the source instead of using
>> debhelper? With that, just have install into /usr/local.
>
> Well, apparently QEMU's build system strips the binaries on it's own so
> debhelper is irrelevant to this particular problem. Anyway, after
> moving /usr/bin/strip out of the way and symlinking that to /bin/true, I
> have a backtrace I hope will be of use to Fabrice or someone else:
<snip>
--
Leonardo E. Reiter
Vice President of Product Development, CTO
Win4Lin, Inc.
Virtual Computing that means Business
Main: +1 512 339 7979
Fax: +1 512 532 6501
http://www.win4lin.com
next prev parent reply other threads:[~2006-08-23 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 0:02 [Qemu-devel] glibc abort if -snapshot is used Andrew Barr
2006-08-23 3:40 ` Rene Horn
2006-08-23 16:14 ` Andrew Barr
2006-08-23 16:48 ` Leonardo E. Reiter [this message]
2006-08-23 21:55 ` Stefan Weil
2006-08-23 22:00 ` Stefan Weil
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=44EC86D7.60008@win4lin.com \
--to=lreiter@win4lin.com \
--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).