Part of it is by default the 4 series will automatically log you out after 20 minutes of "inactivity" but the?activity counter seems to only be reset on traffic from you to the processor -- the processor sending you things [such as just passively running
Debugger to try to catch something]?doesn't count.
The good news is that if you are mindful of the security implications of doing so you can change or disable the timeout via a simple console command
toggle quoted message
Show quoted text
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:
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.
??
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.?
