Working with Pako, we created a macro based on Directory watcher and File Monitor that triggeres an event when a specific text string appears in a log file.
I have shown that this works but every so often, I notice that EventGhost is no longer running and I have to restart it. I strongly suspect the macro we created is causing the problem (If I disable the macro Eventghost always runs) but I can't figure out how to debug the application and figure out where the crash is occuring. Once I get that far, I can start putting in debug code to try to figure out what is going on.
Does EventGhost have a log file where the crash might be logged?
Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.
EventGhost Crashes when runing macro
-
ijourneaux
- Experienced User
- Posts: 102
- Joined: Wed Feb 17, 2010 2:20 am
Re: EventGhost Crashes when runing macro
If you run EG with the -debug switch it will log extra messages. It will also create a log.txt file with the messages, including ones that aren't shown when the program is shutting down. On Vista/Win7 the file is in "C:\Users\<Name>\AppData\Roaming\EventGhost". I forget where it is on XP.
Brett
Brett
-
ijourneaux
- Experienced User
- Posts: 102
- Joined: Wed Feb 17, 2010 2:20 am
Re: EventGhost Crashes when runing macro
Thanks. I will have to get my head wrapped around the problem again but this should get me the information i need to start debugging.