🚀 go-pugleaf

I am having this wierd problem with a program I am writing.  Basically,
the program adds menus to the workbench window and allows you to run
programs from there.

When a workbench program is run and terminated, and then another
program is run that looks up a path, the machine gurus.  Right now, it
is implemented as a process that is started via LoadSeg/CreateProc.  If
I change the program to do a Execute("RUN blah blah") to load in the
handler, it doesn't guru (it will guru when the starting CLI goes away
and something is run).

If I comment out the line in wbfree() (that frees up memory for replied
WBStartups) that does an UnLock, then I don't guru either.  If the code
for searching paths is not used, then I don't guru either.  I suspect
that either that I am trouncing on memory, or that the Process
structure is not set up correctly.

If I don't figure this out, then I will probably just use the program
without path searching compiled in, post it for general amusement,
and hope that someone figures something out.

Running CLI programs and path searching is done from a much modified
RunBack.c, and the workbench running code is done via a hodgepodge of
things (I found WBRun and something from Pete Da Silva after I was 90%
done).  The handler is started up much the same way as dmouse.

Any hints will earn eternal gratitude.

-- 
Darin Johnson (leadsv!laic!darin@pyramid.pyramid.com)
	Can you "Spot the Looney"?