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

Curry Kenworthy curry at pair.com
Fri Feb 21 13:53:53 EST 2020

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

More information about the use-livecode mailing list