On 17 May 2006 John Tytgat <John.Tytgat(a)aaug.net> wrote:
In message <cdf981284e.pnyoung(a)pnyoung.ormail.co.uk>
Dr Peter Young <pnyoung(a)ormail.co.uk> wrote:
> On 17 May 2006 Paul Vigay <lists-nospam(a)vigay.com> 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
I understand less of this now than I did, not that I understood it
If I go back to the old setting in Keystroke, I now get a different
error message, and the computer doesn't lock up. Best demonstrated by
what happens if I shift-drag NetSurf's full filename into a task
Cannot open <Wimp$ScrapDir>.WWW.NetSurf.Log for I/O redirection
This is exactly the message I get with an attempt to run NS the second
time from the incorrect keystroke.
However, even odder:
If I do the same shift-drag into a task window when NS isn't already
running, I get a separate error window from NS saying "Window manager
is already in use".
Should I tell the bug tracker about this?
With best wishes,
Peter \ / \ Prestbury, Cheltenham, Glos. GL52
Anne \ / __ __ \ England.
and / / \ | | |\ | / _ \ http://pnyoung.orpheusweb.co.uk
family / \__/ \_/ | \| \__/ \______________ pnyoung(a)ormail.co.uk.