Thanks, I figured this problem out this afternoon (now on to the others :)
Turns out that the "library" code I was using was using user level memcpy.

   - Chris

BTW: I am currently having a problem that if I load, unload, and then load
again my system seems to freeze.  I can tell the driver is still running (it
prints a debug message every second) and kldload does return, but if I try
and do anything it just freezes (ls, kldunload, etc).  Any ideas.

  - Chris

----- Original Message -----
From: "Alfred Perlstein" <[EMAIL PROTECTED]>
To: "Chris Ptacek" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, March 30, 2001 1:03 PM
Subject: Re: Page Fault problem with my KLD


> * Chris Ptacek <[EMAIL PROTECTED]> [010330 09:45] wrote:
> > I am developing a KLD and I am having problems getting a page fault.  I
am
> > using a set "library" (basically a set of third party object files I
build
> > and then link in).  This libarary requires its own chunk of memory that
it
> > manages and needs to be passed a pointer to that memory (and the size)
when
> > it is initialized.  So during my load phase I malloc the memory (14M),
at
> > this point I can traverse the memory just fine using a for loop writing
and
> > reading from it as a test.  However once I pass this memory into the
> > "library" to use, I get a page fault error.  Is there something I am
missing
> > here?  What would be the possible causes of the page fault?
>
> Page faults are caused by referencing memory that you shouldn't.
>
> See: http://www.freebsd.org/handbook/kerneldebug.html
>
> > Any and all help would be appreciated and if you could CC this account I
> > would appreciate it (my FreeBSD mailing list subscriptions are from
another
> > account).
>
> Next time offer a test snippet of code that demonstrates the problem.
>
> --
> -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
> Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to