Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Trace file Issue while app is crashing

  1. Issue
0
Votes
Undo
  1. Dinesh Babu Sivakumar
    Dinesh Babu Sivakumar
  2. PowerBuilder
  3. Thursday, 16 January 2020 19:31 PM UTC

Our application is crashing randomly so I enabled tracing to see what is causing this Appcrash.

I got an issue by enabling Trace but trace file is not opening and popping out with the below error message.

 

After this, I opened our application normally with the same path & same trace file by overwriting and it was opening fine. Since it was appcrash issue, its not opening in profiling view or whether it can be opened in any other way to see what was the point to cause this issue.

 

 

 

Not finding the RibbonBar and other enhancements w...
Disconnect the Transaction
Responses (2)
René Ullrich
René Ullrich Accepted Answer Pending Moderation
  1. Friday, 17 January 2020 07:14 AM UTC
  2. PowerBuilder
  3. # 1

I think it is normal behaviour after a crash. Trace file will be corrupt if application crashes.

So you can't use tracing to find why an application crashes. For this it is better to use the PBDebug feature. It writes a text file that you can check after a crash. But PBDebug is much more slower than tracing.

HTH,

René

Comment
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 16 January 2020 22:45 PM UTC
  2. PowerBuilder
  3. # 2

The first question is....have the conditions in the error message been met?

1. Put all your PBLs, PBDs, the EXE into the same folder.
2. Define your tracefile so that it resides ion the same folder as #1 above.
3. Add thefull path name of the tracefile into the PB.INI file to get the relevant source code (if you wish).
4. Run the app and wait for it to crash.
5. Get into the tracefile and explore!


Later -

Olan

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.