RE: ucontext.h
pramod sharma <[email protected]> Sun, 10 Oct 2004 02:05:21 -0700 (PDT)
| Newsgroups | gmane.linux.redhat.ia64.general |
|---|---|
| Message-ID | <[email protected]> |
Thanks Tian , For giving me the correct direction ..I am on my way almost to finish that . Pramod --- "Tian, Kevin" <[email protected]> wrote: > >-----Original Message----- > >From: [email protected] > [mailto:[email protected]] On > >Behalf Of pramod sharma > >Sent: Wednesday, October 06, 2004 2:56 PM > >For the intel x86 , running on Linux, > >the struct ucontext *ucp ; > >ucp->uc_mcontext.gregs[ERR]" field can be used to > find > >out whether READ or WRITE caused the page fault. > This > >field simply means that we get the interrupted > >instruction from ucontext (saved user context) and > >check whether it is read or write. > > > >but for IA -64 , there is no structure defined like > >this .......is this not supported for IA64 . > > > > > >How can I acheive this in IA64 ? > > > >Any pointers in this direction will be helpful. > > > >Regards > >Pramod > > Hi, Pramod, > Checking siginfo should be enough to retrieve > necessary info > about fault (Si_code and si_errno). Like SEGV_ACCERR > for si_code stands > for invalid permissions for destination, including > both read and write > operations. Furthermore, ISR is kept in siginfo for > SIGSEGV, etc, which > describes complete faulting info, like r/w/x. You > can refer to manuals > for ISR details. > > Thanks, > Kevin > > _______________________________________________ > ia64-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/ia64-list > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com