In message <cdf981284e.pnyoung(a)pnyoung.ormail.co.uk&gt; Dr Peter Young <pnyoung(a)ormail.co.uk&gt; wrote: > > On 17 May 2006 Paul Vigay <lists-nospam(a)vigay.com&gt; wrote: > > > > > I've noticed recently that about 1 in every 5 times of loading NetSurf, I > > get the error message "UnixLib detected recursion of signal SIGSEGV. > > Exiting." when I double-click on NetSurf - before it appears on the icon > > bar or anything. > > > > The error message is written directly (VDU4?) to the screen, and not in a > > wimp error window. As soon as this occurs, any attempt to use the machine > > results in a 'Filecore in use' error message and I have to reset the > > machine. > > > > Has anyone else experienced this? > > Yes, I used to get this, and it turned out to be all my fault; > however, this may not be relevant to Paul's problem. > > Being lazy, I usually run NetSurf from a keystroke in !Keystroke (now, > I wonder, does Paul use NextBar?) My mistake was to have just > NetSurf's full pathname in Keystroke's setup window, instead of having > it preceded with Filer_Run. This worked fine the first time NS was > run; however, if it was already on the icon bar, which I had > forgotten, and tried to run it again from Keystroke, I got exactly the > same error message, and in the same manner, that Paul describes. > > Having got the correct syntax in Keystroke it's never happened again. I wouldn't describe this as your fault. The "UnixLib detected recursion of signal SIGSEGV." is serious internal error usually meaning the program itself got corrupted. No matter how you've started NetSurf, this shouldn't happen. I would be interested to know what's going on here but I can not reproduce this on my RPC Adjust using Keystroke demo v4.01. Anyone else can ?

In message <a0fdd7284e.pnyoung(a)pnyoung.ormail.co.uk&gt; Dr Peter Young <pnyoung(a)ormail.co.uk&gt; wrote:

> Should I tell the bug tracker about this? No, at least not for me. Those error messages are very explainable and don't mean there is a hidden & serious problem. The first one is because the output of NetSurf is redirected to the file <Wimp$ScrapDir>.WWW.NetSurf.Log and when trying to start a 2nd instance of NetSurf, you can't write to the same file. And the 2nd one is because you can't start a Wimp task in another Wimp task (TaskWindow) just like you are doing. I'm really after a reproducable "UnixLib detected recursion of signal SIGSEGV." case if there is still such a case.