From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19OyLD-0005bt-Pz for qemu-devel@nongnu.org; Sun, 08 Jun 2003 07:28:03 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19OyL0-0005W6-NT for qemu-devel@nongnu.org; Sun, 08 Jun 2003 07:27:51 -0400 Received: from mx02.uni-tuebingen.de ([134.2.3.12]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19OyHQ-0004gI-OY for qemu-devel@nongnu.org; Sun, 08 Jun 2003 07:24:08 -0400 Received: from oldeoog (semeai.Informatik.Uni-Tuebingen.De [134.2.15.66]) by mx02.uni-tuebingen.de (8.12.3/8.12.3) with ESMTP id h58BNuKW007854 for ; Sun, 8 Jun 2003 13:24:01 +0200 Received: from falk by oldeoog with local (Exim 3.35 #1 (Debian)) id 19OyH8-0000N7-00 for ; Sun, 08 Jun 2003 13:23:50 +0200 Subject: Re: [Qemu-devel] Sparc port References: <3EE30B8E.5070600@free.fr> <20030608.032040.08328976.davem@redhat.com> <3EE3158B.5090901@free.fr> From: Falk Hueffner Date: 08 Jun 2003 13:23:39 +0200 In-Reply-To: <3EE3158B.5090901@free.fr> Message-ID: <87adcsn77o.fsf@student.uni-tuebingen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Reply-To: qemu-devel@nongnu.org List-Id: List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , To: qemu-devel@nongnu.org Fabrice Bellard writes: > BTW, another question: how can we know on Sparc if a SIGSEGV or > SIGBUS was generated because of a read or a write ? Probably in the same ugly way I tried it in the Alpha port: look at the faulting instruction and disassemble it. > The Linux kernel has the info but it does not seem to be copied to > user space. It may be interesting to find a standard way to indicate > if it is a read or write which caused the fault (using a field in > siginfo_t would be nice). Yes, that would be really nice. There are many uses for this. -- Falk