KEY searches causing Accordance to crash

[Λύχνις Δαν]

Hi ya,

 

I was trying out a few things in relation to this post : http://www.accordancebible.com/forums/index.php?showtopic=10035.

 

If I open NAS95S and enter "[KEY G134?(0 1 2 3)]", or "[KEY G134?(1 - 9)]", note the spaces either side of the "-", these will crash Accordance 10.1.7.

 

All I can find in the system logs is :

7/1/13 5:53:47.471 PM com.apple.launchd.peruser.501[167]: ([0x0-0x7027020].com.OakTree.Accordance[2071]) Exited with code: 217

So does "[KEY *(G1341, G1349)]".

 

And "[KEY G13?(1 2)?]"

 

So basically I think there is a problem with spaces in the KEY arguments.

OK, its not just spaces. "[KEY 134?(-9)]" also crashes.

Also "[KEY G134?(2,,9)]" crashes.

 

I'll stop now but basically there are a bunch of invalid cases that blow up Acc.

 

Thx

D

Edited July 2, 2013 by Daniel Semler

[Ken Simpson]

This is reproducible for me in the aleph as well

[Λύχνις Δαν]

I'm sorry Ken I don't quite parse that - do you mean its broken for Hebrew also ?

 

Thx

D

[Ken Simpson]

No, it's just a flag to our developers that it's also broken in the next test build which is nearing release.

 

Sorry to be cryptic.

[Λύχνις Δαν]

I was wondering if you meant alpha release. Ok, good to know.

 

Thx

D