Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!mintaka!mit-eddie!uw-beaver!cornell!rochester!pt.cs.cmu.edu!spice.cs.cmu.edu!af
From: af@spice.cs.cmu.edu (Alessandro Forin)
Newsgroups: comp.os.mach
Subject: Re: using Mach exceptions and Unix signals in the same task
Summary: yes, see GDB
Message-ID: <11738@pt.cs.cmu.edu>
Date: 31 Jan 91 15:01:38 GMT
References: <1991Jan30.150711.8040@mintaka.lcs.mit.edu>
Organization: Carnegie-Mellon University, CS/RI
Lines: 18


Although I find the use of signals despicable.. yes you can do that.
All you need is to grab your old exception port and stash it away,
replace it with one of your own ports, stick a thread to listen to
that port.  When an exception message comes, either handle it yourself
or forward the exception message on to the old exception port.

For a practical example, look at what the Mach GDB does.  I presume
sources should be part of the distribution, if not there is a copy
on wb1.

BTW, the instructions for FTPing from CMU clearly indicate that we
run secure FTP daemons: you can only "cd" to the prescribed directories,
any attempt to move elsewhere (INCLUDING intermediate directories)
is prohibited.

Hope this helps,
sandro-