From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] qemu-i386 segfaults running "hello world".
Date: Sun, 24 Jun 2007 01:40:52 -0400 [thread overview]
Message-ID: <200706240140.52617.rob@landley.net> (raw)
In-Reply-To: <523491B7-959A-4CDE-A821-CD87F75D4DB4@suse.de>
On Saturday 23 June 2007 03:27:03 Alexander Graf wrote:
> I guess you're running on i586 then?
Athlon. (/proc/cpuinfo says "AMD Sempron(tm) 2200+")
> I only tried this on ppc.
> Last time I checked the code-copy stuff was broken, so maybe it helps
> to disable that?
What code-copy stuff? (How do I disable that?)
> If that doesn't work either - would you mind to gdb it and run a "bt"
> when it segfaulted so we can see if the segfault is in the generated
> code?
Sure... except it has no debugging symbols so the backtrace is just numbers
and an occasional library name. How about... Huh, ./configure --help doesn't
show any sort of --enable-debug... Trying "./configure --extra-cflags=-g"...
Nope, that stripped it too. Ok, grep for "strip" and it shows up in multiple
places. It's in ./configure but I can't seem to tell configure not to do it.
Maybe "make STRIP=echo" would work? Nope...
Grrr:
make clean
mkdir sub
ln /bin/echo sub/strip
PATH=`pwd`/sub:$PATH make
Ok, that didn't do it either.
Would somebody like to clue me in on how to get this darn thing to build a
version with debugging symbols, please?
In the meantime:
Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x800773a9 in ?? ()
#2 0x00000001 in ?? ()
#3 0xbff09304 in ?? ()
#4 0xbff0930c in ?? ()
#5 0xb7f75ff4 in ?? ()
#6 0xb7fc77b0 in ?? () from /lib/ld-linux.so.2
#7 0x80077350 in ?? ()
#8 0xffffffee in ?? ()
#9 0xb7f75ff4 in ?? ()
#10 0xb7fd3ce0 in ?? () from /lib/ld-linux.so.2
#11 0x80077350 in ?? ()
#12 0xbff092d8 in ?? ()
#13 0xb7e4ee61 in ?? ()
#14 0x00000001 in ?? ()
#15 0xbff09304 in ?? ()
#16 0xbff0930c in ?? ()
#17 0xb7fbbdcb in ?? () from /lib/ld-linux.so.2
#18 0x00000000 in ?? ()
Kind of useless...
> Alex
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-06-24 5: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 [this message]
2007-06-23 7:41 ` Rob Landley
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=200706240140.52617.rob@landley.net \
--to=rob@landley.net \
--cc=agraf@suse.de \
--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).