1. Bjarne Anker
  2. PowerBuilder
  3. Thursday, 12 March 2020 08:58 AM UTC

Hi.

 

I've gathered profiling information at runtime for one of our customers.

I have a PBP file at my computer and want to open it in "Profiling Trace View" in PowerBuilder 2019 to analyze it.

First I need to choose a target (.pbt) file, and the I get this error:

 

I've chosen to open the target file from which the exe and pbd's are built.

 

Any ideas on how to analyze this trace file properly?

 

br,

 

Bjarne Anker

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 12 March 2020 18:17 PM UTC
  2. PowerBuilder
  3. # 1

Hi Bjarne;

   FYI: The trace file must be located in the same folder as where the PB Target is that you are trying to analyze.

HTH

Regards ... Chris

Comment
  1. Bjarne Anker
  2. Thursday, 12 March 2020 20:52 PM UTC
It does, and still the same error message.

Is there any hardcode paths in the PBP file?

I have my PBL's at d:\PBAPPS\Trading\, but the installation where I grabbed the PBP file is located in c:\Maritech\Trading\

Perhaps this is a problem?



Bjarne
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 13 March 2020 15:03 PM UTC
Hi Bjarne ... As long as you move the PBP file to "d:\PBAPPS\Trading\", it should open up OK when using he PB IDE positioned on that App's same target folder for any of the three viewers.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 4 August 2020 17:33 PM UTC
  2. PowerBuilder
  3. # 2

Hi Everyone;

    Since we are talking about Application Profiling here in this thread. I just wanted to drop you a quick note that I just added a "real time" Application Profile Viewer feature to the latest STD Integrated Framework. The current beta version of the frameworks Demo App can be downloaded from here and is now compiled & tested under the latest PB2019 R2 MR 2353. The real-time viewer feature works when running the App from the PB IDE and it also works from any P-Code or M-Code compiled PB App EXE of either a 32 or 64 bitness.

   The STD framework has had the ability to produce an App Profile Trace file "on demand" for over a decade. However, you then needed to exit the App and then use one of the "Trace Viewer" utilities that can only be launched from the PB IDE in order to look at performance datum. Now you can start, add, refresh & view the App Profile Trace file datum any time while your Unit testing your PB App. Plus, you can even do this in the QA, IT, ST, UAT & Prod environments from any compiled EXE "on demand".

    I have suggested an Elevate 2020 topic for this awesome yet misunderstood and misused feature that I call "Extreme Application Profiling & Tracing" but, I have not yet heard back yet if this topic will be accepted.

Regards ... Chris

 

Comment
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.