Crash-a-lot just became critical

[Colin Holgate]

Is it really the case that LiveCode does no logging to Console at all?

That aside, would a screensharing session with Edinburgh have any value? Them watching it crash might lead to some ideas, without needing the source code.


> On Jan 8, 2015, at 1:21 PM, J. Landman Gay <jacque at hyperactivesw.com> wrote:
> 
> On 1/8/2015 10:41 AM, Dr. Hawkins wrote:
>> It is also unacceptable to expect me to turn over source code with over
>> $100k of development time to be able to try to track down these crashes.
> 
> I understand. But they can't fix it unless they can reproduce it. So you can either trust them or live with it until/unless someone else has the same issue and submits an example. The team is very keen to fix these issues, and crashes take top priority, but you've sort of tied their hands.
> 
> I can verify first-hand that your work will remain confidential, and all files will be deleted after they fix the problem. They are also willing to sign any type of NDA you require.
> 
> I think your only other alternative is to download the source code from github, set up the development environment, and do the trace yourself.
> 
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode