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

Resolved Crash from the IDE ( Urgent )

  1. How-to
0
Votes
Undo
  1. ATK Gimmy Susan
    ATK Gimmy Susan
  2. PowerBuilder
  3. Thursday, 30 May 2019 12:53 PM UTC 
Hi Guru

If I run my project from the IDE I get a crash

What I can see (see attachment) is that the w_frame is drawn very small in the upper left corner.

After a few seconds a crash occurs.

directions?


ty


p.s.
Windows 10
Powerbuilder 2017r3


FileMove and FileCopy Fail on a Windows 2016 Serve...
ADO connection issue in .net assembly
Responses (5)
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 4 June 2019 02:31 AM UTC
  2. PowerBuilder
  3. # 1

I see this issue is marked as resolved. Can you please share with us how it was resolved?

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Sunday, 2 June 2019 07:25 AM UTC
  2. PowerBuilder
  3. # 2

I´ve seen the exact same crash as described by Gimme happen many times in my applications.

After doing a full rebuild it's solved.

Comment
There are no comments made yet.
ATK Gimmy Susan
ATK Gimmy Susan Accepted Answer Pending Moderation
  1. Friday, 31 May 2019 07:07 AM UTC
  2. PowerBuilder
  3. # 3

Making a step by stap is very arduous in that the system goes into error at the beginning.

I tried to activate the trace (see image 1)

and the result is a file that the profiling cannot read (see image 2)

 

I enclose a trace file.

Attachments (1)
am.zip
Comment
Load more comments
ATK Gimmy Susan
  1. ATK Gimmy Susan
  2. Friday, 31 May 2019 09:34 AM UTC


Is there a viewer of the generated file?
  1. Helpful
Brad Mettee
  1. Brad Mettee
  2. Friday, 31 May 2019 12:57 PM UTC
Any text editor/viewer can open a generated with /pbdebug.
  1. Helpful
Michael Kramer
  1. Michael Kramer
  2. Friday, 31 May 2019 19:17 PM UTC
PBDEBUG log file is just a long, long text file.

Log file flushes to disk at every write => app may appear slow.

After crash open logfile in any text editor that can handle large files. File may have > 100'000+ lines.

Scroll to end to find crash point.

Search upwards to unravel call stack when crash occurs.

Use that info to review code. Potentially set debug breakpoints and deep dive with debugger.
  1. Helpful
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 30 May 2019 20:18 PM UTC
  2. PowerBuilder
  3. # 4

Check the Library List to ensure completeness.

Do a full rebuild, as per Michael.

DEPLOY the application to generate the EXE.

Test it again.

If the code still abends, then NOW you can so a step-by-step DEBUG.


Good Luck,

Olan

 

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Friday, 31 May 2019 07:53 AM UTC
Agreed, I cannot offer any other options.



Good luck
  1. Helpful
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Thursday, 30 May 2019 13:11 PM UTC
  2. PowerBuilder
  3. # 5

Hi Gimmy,

PowerBuilder step-by-step debug until the crash occurs?

Best,

.m

 

Comment
Michael Kramer
  1. Michael Kramer
  2. Thursday, 30 May 2019 20:07 PM UTC
I concur with Marco.

First however, full rebuild. May fix issue if caused by compiled code out of sync during development.

Otherwise step-by-step debug until you hit code that makes window small - and later makes app crash.
  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.