1. Balu Krishnasamy
  2. PowerBuilder
  3. Wednesday, 13 January 2021 16:23 PM UTC

Gentlemen, I was being asked by my devops for my application symbol file (running on 2017 R2). The only file that i know of is the ".dbg" on those lines which we would create by running the application with the /PBDEBUG switch. Is my understanding correct? If not, could someone please eloborate on how to generate one? Thanks for your time!

(P.S: this is needed by Microfsoft in order to review our logs alongside the process dump file to troubleshoot some performance issues)

Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 13 January 2021 16:33 PM UTC
  2. PowerBuilder
  3. # 1

(EDITED: changed dbg to pbd, as that's the extension in visual studio)

Powerbuilder is not Microsoft nor .Net. I would tell that in the first place to your Devops. Let them define exactly what they want ... A dbg file like the pbd file, when you compile in visual studio in debug mode? This is powerbuilder.


  1. Balu Krishnasamy
  2. Wednesday, 13 January 2021 18:21 PM UTC
*I cant seem to edit my comment, but on the tabbing it takes more than couple of seconds to set the focus on the next editable control. Also, db retrieval gets bogged down and so as opening any windows. pretty much it feel like any operation you perform on the application is slow to respond.
  1. Helpful
  1. Balu Krishnasamy
  2. Monday, 25 January 2021 21:00 PM UTC
Thought ill update my answer here real quick

Apparently the performance issue is caused by some unit test pbds supposedly that's not packaged with the production code. (the code has really one reference to the unit testing libraries when being invoked by a secret key combo which explains why the app didnt crash with the missing pbd's). Anyways procmon reports that these pbds are not found pretty much all the time while using the application. For some reason the azure platform seem to be sensitive about this resulting in a performance lacking feel while the on-prem cusotmers seemed to not be too impacted but i betcha these files were missing in the on-prem as well. My team member found this theory while reading this link, https://answers.sap.com/questions/9735475/powerbuilder-window-slow-to-open-in-citrix.html .

For testing purpose, We copied the unit testing pbds, the proc mon did report it as missing and the logs we had seemed to have improved drastically as well while in the application.

Thank you for all your thoughts and ideas!
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 25 January 2021 21:13 PM UTC
Thanks for sharing the solution, and glad to hear your issue got resolved!
  1. Helpful
There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.