From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sparc port
Date: 08 Jun 2003 13:23:39 +0200 [thread overview]
Message-ID: <87adcsn77o.fsf@student.uni-tuebingen.de> (raw)
In-Reply-To: <3EE3158B.5090901@free.fr>
Fabrice Bellard <fabrice.bellard@free.fr> 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
prev parent reply other threads:[~2003-06-08 11:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 10:10 [Qemu-devel] Sparc port Fabrice Bellard
2003-06-08 10:20 ` David S. Miller
2003-06-08 10:52 ` Fabrice Bellard
2003-06-08 11:19 ` David S. Miller
2003-06-08 16:21 ` Fabrice Bellard
2003-06-09 5:28 ` David S. Miller
2003-06-08 11:23 ` Falk Hueffner [this message]
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=87adcsn77o.fsf@student.uni-tuebingen.de \
--to=falk.hueffner@student.uni-tuebingen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.