public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@karaya.com>
To: linux-kernel@vger.kernel.org
Subject: What is i386 thread.trapno?
Date: Sat, 02 Jun 2001 21:31:42 -0500	[thread overview]
Message-ID: <200106030231.VAA03708@ccure.karaya.com> (raw)

With a normal segfault, the handler gets a trapno == 14 in the sigcontext.  
With UML, I can make a process infinitely segfault with trapno == 1.  The page 
being accessed is correctly mapped in according to /proc/<pid>/maps, so the 
odd trapno is the only clue that I can see that something is different.

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?
and
	Where's this segfault coming from?

				Jeff



             reply	other threads:[~2001-06-03  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03  2:31 Jeff Dike [this message]
2001-06-03  2:42 ` What is i386 thread.trapno? Keith Owens
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=200106030231.VAA03708@ccure.karaya.com \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox