Update:  The call is apparently asynchronous.

After hitting ENTER as described below, the application finally started about 6.4 minutes later!
I entered my credentials into the app and hit LOGIN.
2 minutes later the application frame was built.
9 minutes after THAT, I'm still waiting for the main interface (a treeview) to be displayed.

After a total od 37 minutes waiting for the main interface to be displayed, I closed the app. That level of performance makes the entire thing useless.

After closing the app, the ".dbg" file appeared in the same folder as the EXE.
Note that the ".dbg" file did not appear at once, it's STILL being populated minutes after the app was closed. Which tells me the entire trace was done in memory rather than being written to as it occurred. No wonder the bloody thing performed so poorly.


Either I'm doing something incorrectly OR the /pbdebug option is simply useless.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

PBv12.1, build 7055
Window 10, 64 bit platform
Oracle 12C database


Is it possible to TRACE a runtime EXE?

The documentation says you can do so from a CMD PROMPT:
           C:\Personal\Testing> EXEFILE.exe /pbdebug

The problem is that when I run the code in this manner, the call just passes through, and the app never starts:

The next to last line was my command: I entered the string, hit ENTER, and the next line of output was displayed two seconds later.


Any thoughts?