gm280
Supreme Mariner
- Joined
- Jun 26, 2011
- Messages
- 14,605
I honestly can't add anything new that hasn't been previously reported. And since the IT folks already know about it, nothing new to add.
I was only wondering if they have the ability to trace where the "Critical Errors" message is coming form in the software and therefore can see what triggers it.
I realize it is a canned message that probably is the go to call for most anything that doesn't flow correctly. But if you know where it is triggered from, then you could use a "Logic Analyzer" preset to trigger when that branch is called to trace what triggers them. Just an idea. I use to write software for years and used a lot of different equipment to catch such things. Sometime it would take days or even weeks before a fault was triggered and that was a real good device to catch it. JMHO
I was only wondering if they have the ability to trace where the "Critical Errors" message is coming form in the software and therefore can see what triggers it.
I realize it is a canned message that probably is the go to call for most anything that doesn't flow correctly. But if you know where it is triggered from, then you could use a "Logic Analyzer" preset to trigger when that branch is called to trace what triggers them. Just an idea. I use to write software for years and used a lot of different equipment to catch such things. Sometime it would take days or even weeks before a fault was triggered and that was a real good device to catch it. JMHO