FYI, there are a couple of third-party Debugger alternatives that I've heard work fairly well. I haven't personally used them, and can't remember the names at the moment, but maybe someone else will chime in. Searching the Group's messages for "debugger" might also turn up something.
toggle quoted message
Show quoted text
--- On Wednesday, January 17, 2024 at 9:32 AM, Jay Basen wrote:
It used to work for me. In the past I have run debugger all night on a
customer's system to catch a weird event that randomly took place. However, I
fully admit that I don't remember which processor series that was on. The fact
that debugger can only run for such short periods of time now, without dropping
a connection to the processor, is just ridiculous and trivializes the
complexity of the systems that are being built for customers.
My $.02
Jay
On 1/17/2024 7:21 AM, johnh via groups.io wrote:
Jay
Only once or twice in all these years I have been able to get debugger to run
for more than a handful of hours. Probably was a 2-series. On these 3 and
especially 4 series even with the idle time set to infinite and even watching
only a small amount of signals, debugger will always find a way to just stop on
its own. Its unreliable for anything after 15 mins or so.
On Tue, Jan 16, 2024 at 08:36 PM, jbasen wrote:
I have SETLOGOFFIDLETIME set to infinte on my CP4 so I can run SimplDebugger
for extended periods of time to capture spurious issues when I'm debugging
driver code. Unfortunately, my experience is that it doesn't work. I still
get disconnects if I try to leave Simpldebugger running for any extended period
of time.
I wish it would work as it has become near impossible to try and capture error
situations that only occur at irregular time intervals.
