PB Classic 12.5.2 Build 5583
OS Doesn't matter
I'm working on tracking down a strange app crashing problem, and the results from /pbdebug would be ideal IF I could turn it on/off as needed within the app.
With no pbdebug off, it takes maybe 15 seconds to get to the response window in the app that's having problems (that's from the time you click the desktop icon to start it). With pbdebug on, it takes 7-8 minutes to get to the window (there's a lot of looping going on to parse multiple datawindows for displaying problem data to the user in a text box). If I could turn on /pbdebug when the response window opens, that would make the app usable and might help find the problem faster. As it is, I can't get debug info because the app never gets to the point where the user can break it. I also can't use the PB Trace tools since they don't close down properly and the trace file is unusable if the app doesn't close it right.
Does anyone know of a way to toggle /pbdebug within a running app?
Brief problem is: at some point on the response window, the internal PB Script processor gets hung, and the entire app stops running code. The strange part is that it doesn't act like an infinite loop since windows keep repainting, and the windows close buttons (corner X) actually works, but no code gets run when you close it. Other buttons click, (depress), but nothing happens. Eventually you need to close the app by killing it from task manager, but it continues painting properly the whole time.