From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1I2KqS-0001ix-DK
	for qemu-devel@nongnu.org; Sun, 24 Jun 2007 01:41:08 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1I2KqQ-0001iP-Sg
	for qemu-devel@nongnu.org; Sun, 24 Jun 2007 01:41:07 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1I2KqQ-0001iK-Lf
	for qemu-devel@nongnu.org; Sun, 24 Jun 2007 01:41:06 -0400
Received: from static-71-162-243-5.phlapa.fios.verizon.net ([71.162.243.5]
	helo=grelber.thyrsus.com)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <rob@landley.net>) id 1I2KqQ-0006Jl-C1
	for qemu-devel@nongnu.org; Sun, 24 Jun 2007 01:41:06 -0400
From: Rob Landley <rob@landley.net>
Subject: Re: [Qemu-devel] qemu-i386 segfaults running "hello world".
Date: Sun, 24 Jun 2007 01:40:52 -0400
References: <200706221715.16729.rob@landley.net>
	<200706230131.20408.rob@landley.net>
	<523491B7-959A-4CDE-A821-CD87F75D4DB4@suse.de>
In-Reply-To: <523491B7-959A-4CDE-A821-CD87F75D4DB4@suse.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706240140.52617.rob@landley.net>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Alexander Graf <agraf@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.