Diagnosing a crasher (was Re: Quality, reputation, and improving both)

dunbarx at aol.com dunbarx at aol.com
Fri Feb 21 15:15:45 EST 2020

We are all fortunate in that you found the culprit in a single command in a line of code.
It crashes LC 9.5.1 in Mac OS. If I change the second parameter (tDel) to a single char, all is well,
The issues I am having with my project occur in random places in different handlers at random times.
This is not stopping me. Saving often allows me to forge ahead, with good results. Been doing this for at least two years.

-----Original Message-----
From: Curry Kenworthy via use-livecode <use-livecode at lists.runrev.com>
To: use-livecode <use-livecode at lists.runrev.com>
Cc: Curry Kenworthy <curry at pair.com>
Sent: Fri, Feb 21, 2020 1:55 pm
Subject: Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

Chiming in again since it dovetails with today's work:

Crashing bugs (and others) sometimes require a missing 
factor/context/detail in the original real-world project that is tricky 
to reproduce in independent test stacks. You have to compensate for that.

I filed this crasher today, but had to use a slightly more "extreme" 
example compared to the original real-project-crasher to get 100% 
reliable open-click-crash independent test stack:

(Save work before running)


Best wishes,

Curry Kenworthy

Custom Software Development
"Better Methods, Better Results"
LiveCode Training and Consulting

use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list