Re: Segmentation fault started with no apparent cause

2016-08-28 Thread Rob Kendrick 
On Sun, Aug 28, 2016 at 09:48:43PM +0100, Andrew Pinder wrote:
> My thought is that one conceivable explanation could be the file had 
> got too big.  It was over 42KB in size.  It seems to have shrunk down 
> to 39KB.

Both these are trivially tiny.

B.

Re: Segmentation fault started with no apparent cause

2016-08-28 Thread Andrew Pinder 
In message <20160826091352.gp26...@platypus.pepperfish.net>
 on 26 Aug 2016 Rob Kendrick  wrote:

> On Thu, Aug 25, 2016 at 10:21:52PM +0100, Andrew Pinder wrote:
>> There appear to be 106 URLs in there.  I'm not going to test each one
>> to find where the problem is.

> Assuming there is nothing personally identifying or secret in your URL
> file, attaching it to the bug would be helpful.

It did occur to me that one way to search for the problem was binary - 
split the file in two and find which half has the problem.  Then 
repeat.  Except after splitting it, neither half caused problems.  
Putting the original back also didn't restore the problem.

My thought is that one conceivable explanation could be the file had 
got too big.  It was over 42KB in size.  It seems to have shrunk down 
to 39KB.

If things are still as clear as mud then waiting to see if anyone else 
has a similar problem may be a good way forward.


Regards

Andrew
-- 
Andrew Pinder

Re: Segmentation fault started with no apparent cause

2016-08-26 Thread Rob Kendrick 
On Thu, Aug 25, 2016 at 10:21:52PM +0100, Andrew Pinder wrote:
> There appear to be 106 URLs in there.  I'm not going to test each one 
> to find where the problem is.

Assuming there is nothing personally identifying or secret in your URL
file, attaching it to the bug would be helpful.

B.

Re: Segmentation fault started with no apparent cause

2016-08-25 Thread Richard Porter 
On 25 Aug 2016 Andrew Pinder  wrote:

> I've tracked the problem down to something in
> Boot:^.!Boot.Choices.WWW.NetSurf.URL

> Moving it elsewhere so it isn't accessible to NetSurf allows NetSurf
> to load normally.  Putting it back brings the problem back.

> There appear to be 106 URLs in there.  I'm not going to test each one
> to find where the problem is.

Just quit NS, delete the contents of URL and re-run NS.

-- 
Richard Porterhttp://www.minijem.plus.com/
Skype: minijem2   mailto:r...@minijem.plus.com
I don't want a "user experience" - I just want stuff that works.

Re: Segmentation fault started with no apparent cause

2016-08-25 Thread Andrew Pinder 
In message 
 on 25 Aug 2016 Andrew Pinder  wrote:

> I've just reported to the bug tracker that NetSurf is now refusing to
> load and exiting with a Segmentation fault.  I have been running CI #
> 3625 since 9 Aug without any problems before this morning.  Reverting
> to #3594 gives the same error.

> Should I delete the files in !Boot.Choices.WWW.NetSurf ?  That strikes
> me as a possible place for a problem to be located that clearly isn't
> in the actual application.

I've tracked the problem down to something in 
Boot:^.!Boot.Choices.WWW.NetSurf.URL

Moving it elsewhere so it isn't accessible to NetSurf allows NetSurf  
to load normally.  Putting it back brings the problem back.

There appear to be 106 URLs in there.  I'm not going to test each one 
to find where the problem is.


Regards

Andrew
-- 
Andrew Pinder