On Fri, Sep 19, 2003 at 03:33:11PM -0400, Dan Sugalski wrote: > So, the sequence is: > > 1) Connect to the control socket > 2) Peg parrot with SIGUSR[12] > 3) Profit! > > No, wait, #3 isn't right... :)
Thinking about it, I don't see why we need #2 either Assuming that we have the event system we've been led to expect, then we'll attach a handler to the debugger socket that gets called on connection. (well, in Unix select terms on being readable) And that handler could kick us into debug mode It seems that screen, emacs client and ssh-agent already create Unix domain sockets in subdirectories of /tmp to provide this sort of service, so I guess this is the right thing for parrot to do (on Unix) Problem solved? Nicholas Clark PS #london.pm's infobot dipsy has been taught a step 4: <dipsy> step 4 is shred all financial documents and give directors bonuses
