You are not logged in.
Pages: 1
Today upgrade (btw, is there a way so see release?)
Start print, after n (random) layers, executable just close and on frontend, obviously, red message "cannot connect.."
n was 2, 12, 8 ....
Does not appear to be RAM issue.
Shutter (LED my case) remains open, if this help to find bug.
Offline
When "working" this is output
Offline
Win32 just crash on starting up display
Offline
I am working on it apparently there is an issue with recently upgraded go 1.8.
Offline
I am working on it apparently there is an issue with recently upgraded go 1.8.
Great!
Offline
I have updated the program, let me know if there is any other issue.
Offline
I have updated the program, let me know if there is any other issue.
I will. [Update, first complete print, yeahhh]
Thank you for support.
Can you share all stdio protocol that server will drop out? It will be useful for me to write down a small utility that monitor server activity and if exception or process shutdown will
power off LED to prevent LCD/LED degradation.
Something like a watchdog, I mean.
Last edited by Gatto (2017-02-23 09:31:13)
Offline
I do not have control over stdio during panic. I would expect panic to be written somewhere. You can checkout golang panic messages to see if you could detect the program termination.
Offline
I do not have control over stdio during panic. I would expect panic to be written somewhere. You can checkout golang panic messages to see if you could detect the program termination.
Can you add argument like -verbose where you mirror to stdio all the log?
will also be easy to > log.txt to see what happened, about panic you can also intercept and write out, maybe will be easier the debug.
Pragram termination is easy to intercept with System.Diagnostics.Process, not yet tested for exit code, anyway.
Offline
You already could do that.
Offline
Pages: 1