as you know, I host an online FPS, however the server costs with using a windows server get a little bit on the high end. My question is, does anyone know of a good solution for logging bgt runtime errors and making the program start up automaticly? I'm using auto it with windows, but my financial state does not allow me to be paying $30 a month for a server that servers hosting an FPS and that's it.
1 (edited by blink_wizard 2017-12-01 03:25:43)
The answer, as cold as it is, is no. BGT runtime errors appear in graphical windows. You can't log those. At all.
In the graphical window unless it's a standard library allocation you can press yes to copy the stack trace to the clipboard. I don't know how wine works but I'd think there's be some way of emulating the windows clipboard, so couldn't something be done that way?
The program actually crashes flat on it's face and exits when the runtime error pops up, because this wine on his servers says something about application tried to create a window and other warnings when you start it. When the runtime window tries to pop up, it ujst flat exits. He might need XServer, since I think it talks about that, but you'd still need to do something strange with I don't even know. As far as I know wine applications cannot interact with each other so we couldn't have the runtime meter intercepting the window. Real shame too, because linux servers give massively awesome pings.
You might be able to take advantage of the crash by having a script that runs in the background checking process information, and relaunches wine when necessary
I just did some searching, I might be able to give a few pointers. These are only ideas, maybe this doesn't work at all, but it is worth trying.
Try intercepting the calls made to the display server with xtrace. You might also need xvfb, I have no idea, completely untested. From what I have red, you can log comunication between the x server and the app by typing:
so this may be:
xtrace wine myapp.exe
Hope this helps someone
golfing in the kitchen
well we're trying to not just relaunch the program if it crashes, but also to log the runtime error like the windows one currently does so we can see what broke.
Yeah, I get that. The runtime error wants to be sent to an x-server, using xtrace might give you the runtime error text if you dig deep enough.
golfing in the kitchen