From: Rik van Riel <riel@conectiva.com.br>
To: afei@jhu.edu
Cc: "M.Jagadish Kumar" <jagadish@rishi.serc.iisc.ernet.in>,
linux-mm@kvack.org
Subject: Re: page fault.
Date: Thu, 26 Oct 2000 17:53:15 -0200 (BRDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0010261752510.15696-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.GSO.4.05.10010261543320.16149-100000@aa.eps.jhu.edu>
On Thu, 26 Oct 2000 afei@jhu.edu wrote:
> On Fri, 27 Oct 2000, M.Jagadish Kumar wrote:
>
> > Is there any way in which i can know when the pagefault occured,
> > i mean at what instruction of my program execution.
> > Does OS provide any support. This would help me to improve my program.
> The way I use is to use oops message and System.map to locate
> the subroutine where the oops occured. To find the exact line
> where the oops occured, you need to either check assemble code
> or use more complicated kernel debug technique. I think Rik
> covered some in his kernel debug slides.
You're confusing issues. A pagefault has NOTHING to do
with an oops...
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-10-26 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 15:52 ptes flags in compressed cache Rodrigo S. de Castro
2000-10-26 15:58 ` Stephen C. Tweedie
2000-10-27 2:12 ` page fault M.Jagadish Kumar
2000-10-26 19:45 ` afei
2000-10-26 19:53 ` Rik van Riel [this message]
2000-10-27 2:14 ` afei
2000-10-27 11:17 ` Stephen C. Tweedie
[not found] ` <8tboe4$3bfb7$1@fido.engr.sgi.com>
2000-10-27 17:38 ` Rajagopal Ananthanarayanan
2000-10-30 12:19 ` volodya
2000-10-27 7:59 ` ptes flags in compressed cache Christoph Rohland
[not found] <8ta1ir$358it$1@fido.engr.sgi.com>
2000-10-26 20:44 ` page fault Rajagopal Ananthanarayanan
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=Pine.LNX.4.21.0010261752510.15696-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=afei@jhu.edu \
--cc=jagadish@rishi.serc.iisc.ernet.in \
--cc=linux-mm@kvack.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