From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-i386 segfaults running "hello world".
Date: Sat, 23 Jun 2007 03:41:19 -0400 [thread overview]
Message-ID: <200706230341.19544.rob@landley.net> (raw)
In-Reply-To: <200706221831.20531.rob@landley.net>
On Friday 22 June 2007 18:31:20 Rob Landley wrote:
> Ok, it's a more fundamental problem:
>
> landley@triolith:/sys$ qemu-i386
> Segmentation fault (core dumped)
>
> Nothing to do with the program it's trying to run, it segfaults with no
> arguments.
>
> Is anybody else seeing this?
>
> Rob
So I'm vaguely suspecting that some of the dynamic linker magic this thing's
doing is contributing to the screw up (or at least the complexity of
debugging it), so I thought I'd statically link.
If I ./configure --static the result doesn't build, it dies during linking.
Is this expected? (Do I need to install .a versions of all the alsa and x11
libraries to make that work?)
I realize releases are a bit out of fashion, but is there any way to go
through cvs to track down which checkin broke this stuff? I can do it in
git, mercurial, or subversion. But cvs isn't really set up for this sort of
thing...
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-06-23 7:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 21:15 [Qemu-devel] qemu-i386 segfaults running "hello world" Rob Landley
2007-06-22 22:31 ` Rob Landley
2007-06-22 23:13 ` Alexander Graf
2007-06-22 23:27 ` andrzej zaborowski
2007-06-23 6:38 ` Rob Landley
2007-06-23 5:31 ` Rob Landley
2007-06-23 7:27 ` Alexander Graf
2007-06-24 5:40 ` Rob Landley
2007-06-23 7:41 ` Rob Landley [this message]
2007-06-23 11:00 ` Jens Axboe
2007-06-24 7:01 ` Rob Landley
2007-06-26 13:05 ` Jens Axboe
2007-06-23 9:50 ` Nigel Horne
2007-06-23 11:12 ` [Qemu-devel] [PATCH] " Stefan Weil
2007-06-24 7:36 ` Rob Landley
2007-07-02 15:02 ` Alexander Graf
2007-07-10 15:47 ` Rob Landley
2007-07-10 16:10 ` Andreas Färber
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=200706230341.19544.rob@landley.net \
--to=rob@landley.net \
--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).