From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HhjcZ-0003Um-RT
	for qemu-devel@nongnu.org; Sat, 28 Apr 2007 05:53:39 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HhjcX-0003QE-Ah
	for qemu-devel@nongnu.org; Sat, 28 Apr 2007 05:53:38 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HhjcX-0003Py-4X
	for qemu-devel@nongnu.org; Sat, 28 Apr 2007 05:53:37 -0400
Received: from ug-out-1314.google.com ([66.249.92.170])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1HhjWZ-0001FX-VV
	for qemu-devel@nongnu.org; Sat, 28 Apr 2007 05:47:28 -0400
Received: by ug-out-1314.google.com with SMTP id j40so835183ugd
	for <qemu-devel@nongnu.org>; Sat, 28 Apr 2007 02:47:26 -0700 (PDT)
Message-ID: <f43fc5580704280247w6fc9c52tc2f192b8f3fb8652@mail.gmail.com>
Date: Sat, 28 Apr 2007 12:47:26 +0300
From: "Blue Swirl" <blauwirbel@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [Qemu-devel] Sparc-linux-user problem
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 <qemu-devel@nongnu.org>

Hi,

I'm investigating why Sparc32 user emulator breaks when linked with
-lrt. It seems that other libraries also cause the problem, for
example -lm -ldl -lX11 -lbfd -lslang is okay, but  -lm -ldl -lX11
-lbfd -lslang -lglib-2.0 segfaults just like -lm -lrt. If just address
space conflict was the issue, I'd think 12 megs libbfd would trigger
the problem instead of 64k librt.

Any ideas?

Good output (DEBUG_SIGNAL enabled):
qemu-sparc ./ld-linux.so.2
qemu: SIGSEGV pc=0x810d80b4 address=4103fd10 w=1 oldset=0x80000000
Usage: ld.so [OPTION]... EXECUTABLE-FILE [ARGS-FOR-PROGRAM...]
You have invoked `ld.so', the helper program for shared library executables.
This program usually lives in the file `/lib/ld.so', and special directives
[cut]

Bad output:
qemu: SIGSEGV pc=0x810d80d4 address=4103fd10 w=1 oldset=0x80000000
qemu: SIGSEGV pc=0x00018000 address=00018000 w=0 oldset=0xfffbfaff
queue_signal: sig=11
qemu: uncaught target signal 11 (Segmentation fault) - exiting

This ld-linux.so.2 is from qemu-tests-0.5.3. The value pc
(=0x810d80d4) changes a bit when libraries are added.