Crash when launching 2.0.7.6

Discussion Forums discussion Crash when launching 2.0.7.6

This topic contains 0 voices and has 7 replies.

Viewing 8 posts - 1 through 8 (of 8 total)
Author Posts
Author Posts
November 3, 2006 at 1:52 am #138

RoryM
Member

I’ve installed 2.0.7.6 on two machines – on one it works just great. On the other it crashes when the app first starts up.

I’ve got the dump file (I’ve since reverted to the ella build) if anyone would like to take a look at it.

November 3, 2006 at 6:51 am #15184

RoryM
Member

Well, I’ve finally gotten pn to build. That at least is something. Something is not right with things.

The first problem I found was in styles.cpp line 59. The response length was zero, so there was a bit of a problem with a negative index !

I don’t yet know why the response is empty, or even what the response is.

This’ll fix it:

if(response.length()> 1 && response[response.length()-1] == ‘ ‘)


Next problem occurs when the “output” scheme is loaded. I’m not sure what’s going on as yet, but, I did notice two sets of schemes are being loaded.

November 3, 2006 at 11:46 am #15185

simon
Key Master

Ok, I’m glad you’ve got this far. I’ll have a look at these errors tonight hopefully.

November 3, 2006 at 10:54 pm #15186

simon
Key Master

Also, please send that dump file to ss at pnotepad dot org. Thanks.

November 4, 2006 at 5:37 pm #15187

zennehoy
Member

Just out of curiousity, do you check bug reports simon, or do you prefer we post such things here? I posted the response.length bug on sourceforge already a few days ago,

Zen

November 5, 2006 at 3:58 pm #15188

RoryM
Member

I should have looked there first. There is this rather vague bug:

[ 1436521 ] crash IDE : Programm have crash after start it.

November 5, 2006 at 8:06 pm #15189

simon
Key Master

Hi, yes I do check bugs, I try to get to them as I can but obviously sometimes these things just take time. Rory do you still see your problem with the most recent code because a couple of crash bugs in the latest autocomplete code have been fixed.

November 6, 2006 at 10:10 pm #15190

RoryM
Member

I refreshed the codebase, and it appears to be fixed. Thanks.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.