Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!cs.utexas.edu!geraldo.cc.utexas.edu!slip-4-4.ots.utexas.edu!vax From: vax@slip-4-4.ots.utexas.edu (VaX#n8) Newsgroups: comp.unix.bsd.netbsd.misc Subject: [Q]: Who is port-i386 maintainer? Date: 30 Aug 1995 22:07:57 GMT Organization: The University of Texas at Austin, Austin, Texas Lines: 26 Message-ID: <422nft$g3e@geraldo.cc.utexas.edu> NNTP-Posting-Host: slip-4-4.ots.utexas.edu X-Newsreader: TIN [version 1.2 PL2] I need to reach the port-i386 maintainer. I am thinking about updating the "faulted-upon address" patch (port-i386:851) if it needs it, and encouraging him to include it. It would help my research project IMMENSELY if this patch were included in the next stable release of NetBSD. I am writing a trace tool that depends on getting the faulted-upon address, and I'd like to not have to distribute a patched kernel with it. The general idea of the patch is to make a hardware register of the x86 MMU, called "cr2", available to a signal handler. This is useful if you wish to figure out what effective address caused a protection fault, for example. Without the effective address is it sometimes hard to deal with the signal appropriately. Consult the patch for more info. (Frankly, I don't know how to access the gnats database myself. Someone mailed the patch to me). Many other OS's have implemented similar or identical techniques. If you know the port maintainer personally maybe you can put a word in as well; I'd really like to get something done in this area, even if it isn't this exact patch. -- MAIL TO THIS ADDRESS: vax@ccwf.cc.utexas.edu Ask me about BSD Unix for your PC for FREE! (NetBSD) - Yes, it runs fast! Victimless crimes are a figment of the state's collective imagination.