From: Keith Owens <kaos@ocs.com.au>
To: Jeff Dike <jdike@karaya.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is i386 thread.trapno?
Date: Sun, 03 Jun 2001 12:42:38 +1000 [thread overview]
Message-ID: <17271.991536158@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 02 Jun 2001 21:31:42 EST." <200106030231.VAA03708@ccure.karaya.com>
On Sat, 02 Jun 2001 21:31:42 -0500,
Jeff Dike <jdike@karaya.com> wrote:
>The i386 page fault handler sets trap_no to 14, so the fault isn't coming from
>there, but I can't see where a SIGSEGV is being delivered to a process with
>thread.trap_no == 1.
>
>So:
> What do these trap numbers mean?
> Where can I read about them?
Intel Architecture Software Developer's Manual Volume 3: System
Programming. Interrupt and Exception Handling, table 5.1 (postscript
extract of that table has been copied in separate private mail).
intel-ia32-arch-vol3-24319202.pdf.
>and
> Where's this segfault coming from?
Probably do_debug() which sets trapno = 1 and also uses
handle_vm86_trap(,,1).
next prev parent reply other threads:[~2001-06-03 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-03 2:31 What is i386 thread.trapno? Jeff Dike
2001-06-03 2:42 ` Keith Owens [this message]
2001-06-03 11:16 ` Alan Cox
2001-06-03 17:32 ` Jeff Dike
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=17271.991536158@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.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.