1. Dexter Madrinan
  2. PowerBuilder
  3. Monday, 19 September 2022 04:12 AM UTC

Hi Guys,

As a result of migrating our source code from PB 2019R3 to PB 2022, the application PB IDE is crashing/terminating during the full build process. What is the problem for this and how to resolve this issue?

 

Your advice is highly appreciated.

 

Thanks.

 

Dexter P Madrinan

 

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 20 September 2022 01:03 AM UTC
  2. PowerBuilder
  3. # Permalink
That's awesome news Dexter! :-)
Comment
There are no comments made yet.
Dexter Madrinan Accepted Answer Pending Moderation
  1. Tuesday, 20 September 2022 00:40 AM UTC
  2. PowerBuilder
  3. # 1

Hi Guys,

 

Thanks for all the advice. My issue was resolved by optimizing the library where the crash occurs.

 

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Monday, 19 September 2022 21:20 PM UTC
  2. PowerBuilder
  3. # 2

Bite the bullet and just manually regen EVERY object in EVERY PBL.

Yes, it's a pain, but it's the ONLY way to be SURE that each of your objects are correct. Odds are excellent that you have an object that no longer compiles correctly after the migration. THIS technique will allow you to find that object and get a better error message.

Set "X" to the first PBL in your library list.

1.  Open PBL X
2.  Select all objects
3.  Regenerate
4.  Release the objects, right click in the LIbrary Painter and select Optimize on that PBL
5.  Set "X" to the next PBL in your library list.
6.  Return to step 1.
7.  Repeat until you've checked ALL your PBLs.

Comment
There are no comments made yet.
Dexter Madrinan Accepted Answer Pending Moderation
  1. Monday, 19 September 2022 11:31 AM UTC
  2. PowerBuilder
  3. # 3

Hi Chris,

 

Thanks for your reply. This I didn't try. I'll try this one and let you know.

Comment
There are no comments made yet.
Dexter Madrinan Accepted Answer Pending Moderation
  1. Monday, 19 September 2022 11:19 AM UTC
  2. PowerBuilder
  3. # 4

HI Andreas,

 

To determine which particular object it refers to is so hard because it stops on one of the menu, the confusing part is before starting the build the particular library were it stops is regenerated successfully. Any other suggestion?

 

Comment
  1. Berka Frenfert
  2. Monday, 19 September 2022 12:03 PM UTC
if crash debug dialog box opens, i do not click on its button and try to see what was the last object in regeneration/build process. ( the lower output pane of PB IDE) Note name of the object in the last line. close the system debug dialog. Reopen PB IDE and regenerate the object. most probably PB IDE will crash again. This confirms the corrupt object. reopen PB IDE and edit that object's source, fix the problem and then regenerate the object.



sometimes parent object when changed , i see error like 'you need to define event/function before you can use it', and i knew nothing was wrong with the parent object. but instead of regenerating parent object i go regenerate child object. Parent object then regenerated after successfully regeneration of child.



The PB IDE output window on crash if still there because of system debug dialog box was opened by windows, sometimes makes bug tracking a lot easier..

  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 19 September 2022 11:15 AM UTC
  2. PowerBuilder
  3. # 5

Hi Dexter;

  Have you tried optimizing all your PBLs after the migration but before the full build?

Regards ... Chris 

 

Comment
There are no comments made yet.
Andreas Mykonios Accepted Answer Pending Moderation
  1. Monday, 19 September 2022 10:20 AM UTC
  2. PowerBuilder
  3. # 6

If you have a project, then you may try to do a full build using pbc220 or pbautobuild. It may also fail, but you will be able to see what was the object it was working on. Probably your issue will be in that object or in one referenced by it.

Andreas.

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 19 September 2022 09:32 AM UTC
  2. PowerBuilder
  3. # 7

Hi,

In some previous version (pb2017?), I had the same problem, but ... When doing a full build by doing a right mouse click on the target and choosing "Full build" from the contextual menu it would always work though.

Maybe it'll solve your problem.

regards,

MiguelL

Comment
  1. Miguel Leeuwe
  2. Monday, 19 September 2022 10:11 AM UTC
Other than by checking the windows event viewer or using the ProcessMonitor tool I wouldn't know of any log files.

https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

and

https://www.technewstoday.com/how-to-use-process-monitor/

Maybe a re-install of PB ?

Good luck!
  1. Helpful
  1. Dexter Madrinan
  2. Monday, 19 September 2022 10:51 AM UTC
Done reinstallation , same thing happens.
  1. Helpful
  1. Andreas Mykonios
  2. Monday, 19 September 2022 11:13 AM UTC
Well, this problem happens if you do a full build in a specific application or with any application (example: sample applications provided by appeon)?

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