- Aron Cox
- PowerBuilder
- Tuesday, 18 June 2024 01:14 PM UTC
PowerBuilder 2019 2728
I am trying to work out exactly which bit(s) of code are slow for a particular customer. I turned on tracing in code for a particular routine, and after a couple of weeks have lots of PBP files. However when I try to open any of them in the Profiling Trace View tool, PowerBuilder exits with no error message. I can open them in the two other Profiling tools, but I don't think that helps me work out which line(s) of code was slow.
Can anyone recommend another tool to view these files, or a way to stop PowerBuilder crashing when I try to view them?
Thanks.
If it's any help the Windows Event Log shows this on PowerBuilder crash:
Faulting application name: PB190.exe, version: 19.2.0.2728, time stamp: 0x6100e4a4
Faulting module name: PBSHR.dll, version: 19.2.0.2728, time stamp: 0x6100e41c
Exception code: 0xc0000005
Fault offset: 0x00148744
Faulting process ID: 0x2ef8
Faulting application start time: 0x01dac17c8a2ef6f7
Faulting application path: F:\Program Files (x86)\Appeon\PowerBuilder 19.0\PB190.exe
Faulting module path: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 19.2.0.2728\PBSHR.dll
Report ID: 8e2566e5-eca4-492b-9c73-ed9ad2027123
Faulting package full name:
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.