From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1C2PoT-0005BV-N2
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 03:45:49 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1C2PoR-0005BJ-Lt
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 03:45:48 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1C2PoR-0005BG-Bu
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 03:45:47 -0400
Received: from [213.165.64.20] (helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1C2Pj3-0007xD-OP
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 03:40:14 -0400
Message-ID: <41357C59.2090000@gmx.com>
Date: Wed, 01 Sep 2004 09:38:01 +0200
From: "Bochnig, Martin" <mb1x@gmx.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] QEMU on SPARC host - Summary and suggested vl.c PATCH
References: <1F40E42A-FBDA-11D8-9481-003065C7D858@mandrakesoft.com>
In-Reply-To: <1F40E42A-FBDA-11D8-9481-003065C7D858@mandrakesoft.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Reply-To: bochnig@pool.math.tu-berlin.de, 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

Gwenole Beauchesne wrote:
> Hi,
> 
>> As I reported recently, I got qemu0.6.0 compiled both under Linux 
>> (Suse7.3, Debian3.0 r2) and Solaris10 both running on HyperSPARC and 
>> UltraSPARC_IIi.
>> Unfortunately the emulation engine libqemu.a doesn't appear to work.
> 
> 
> Not sure if that helps but something worth knowing about is you need a 
> kernel recent enough or specific Dave S. Miller patch to get accurate 
> address in si_addr member of siginfo_t.  Otherwise, the reported address 
> is truncated to page boundaries IIRC. Or, you would need to decode the 
> instruction and possibly traverse the register windows.

Hi,

I'm afraid you're right.
Sounds plausible.
I surfed dyngen.c and tried to figure out, how/when the error messsages
are to be produced.
I may need help in order to get it running (especially for Solaris 10).
I may have to learn SPARC assembly?

Many thanks,
Martin


> 
> Bye,
> Gwenolé.
> 
> 
>