Author Topic: ZeroBrane debugging only lasts 300-900 seconds. Why?  (Read 309 times)

Offline mrslother

  • Sr. Newbie
  • *
  • Posts: 29
  • Karma: +0/-0
ZeroBrane debugging only lasts 300-900 seconds. Why?
« on: October 23, 2016, 04:34:16 pm »
Any code I debug in ZeroBrane will last only (roughly) 300-900 seconds before it is terminated. Note the code does not exit, rather the execution is terminated (the code is a while(true) loop).

ZeroBrane suggests that all is good:
Code: [Select]
Debugging session completed (traced 0 instructions).
Program completed in 481.28 seconds (pid: 8740).

Is this due to the Vera Lite terminating the process, the ZB terminating the process or something else?
...and how do I change this so that the debug session can last as long as needed?

Offline paulclinger

  • Jr. Member
  • **
  • Posts: 84
  • Karma: +5/-0
Re: ZeroBrane debugging only lasts 300-900 seconds. Why?
« Reply #1 on: March 14, 2017, 12:00:14 am »
> Is this due to the Vera Lite terminating the process, the ZB terminating the process or something else?

(just noticed this message) @mrslother, this looks like VeraLite is closing the socket, which is detected as completion of the debugging session on the IDE side (and those messages are shown as the result). There is nothing on the IDE side that can be changed to affect that as the IDE is waiting for the results sent from the debugger in the application (that is running on the device).

Is there anything relevant in the logs? Are there any settings on VeraLite that can control the socket timeout?