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

Resolved Debugging a build

  1. How-to
0
Votes
Undo
  1. Kevin Bey
    Kevin Bey
  2. PowerBuilder
  3. Friday, 2 November 2018 14:28 PM UTC

Looking for help trying to debug a 'build'. 

Running the 'Deploy Project' process on this particular application appears to run as normal.  Then it finishes with a generic 'Appeon PowerBuilder 2017 R3 has stopped working' message. 

All of our other applications using on the same baseline source code and objects build correctly.  The code that's failing in PB2017R3 builds correctly in PB 12.5.2 .

Is there any way to 'debug' the 'Deploy Project' so I can see what's causing the error?

Thank you

Is there a way to dynamically scroll a datawindow ...
Foxit SDK for Windows
Responses (4)
Kevin Bey
Kevin Bey Accepted Answer Pending Moderation
  1. Tuesday, 20 November 2018 14:51 PM UTC
  2. PowerBuilder
  3. # 1

Hi Miguel,

You sir, are a rock star!!  Right-clicking on the menu item seems to have worked.  I am running 2 versions of PB on the same pc, but will reinstall 2017 again when I'm able to lose the older version.

Thanks for your help!

KB

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 20 November 2018 18:45 PM UTC
YW, I'm very convinced that pb12.6 and pb2017 don't get along very well on the same PC. Make sure you separate your DLL's (shared folders) totally from both installations when you do the re-install.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 20 November 2018 19:08 PM UTC
Hi Miguel;

FWIW: I have PB 11.5.1, 12.1, 12.5.1, 12.6 and PB2017 running on all my real machines (not VM's). Since June of 2017, I have installed PB2017 among all those PB versions as well, with no issues. I'll be adding PB2018 at the end of this month to that list as well (beta test).

FYI: Check out my Elevate2018 conference presentation on the PB IDE Tips & Tricks for more information on how I manage different PB versions and even various MR's & EBF's of the same PB release in my development environment.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Tuesday, 20 November 2018 08:02 AM UTC
  2. PowerBuilder
  3. # 2

How are you running the deploy?

This might sound weird but:

I have (had?) the problem of pb2017 blowing up when doing a deploy from a project object.

When running it using right-mouse-button and selecting "deploy" from the contextual menu, it works.

 Are you running the powerbuilder ide "as administrator" or not? Try switching that.

Do you have another older version of powerbuilder installed on the same PC? If so, uninstall and re-install pb2017 completely. I've had to do that several times.

 

HIH

 

Comment
There are no comments made yet.
Kevin Bey
Kevin Bey Accepted Answer Pending Moderation
  1. Monday, 19 November 2018 19:38 PM UTC
  2. PowerBuilder
  3. # 3

Hi Chris,

So far, I've optimized all libraries, performed clean builds on our other applications, and verified that my work folder and sub-folders do not have write protected folders/files.  I do have some Informational messages generated when building all of our applications, but these don't display error messages at the end of the build process.

A majority of the Informational messages are the result of instance variables declared in a parent object, and again in a child object.  I've cleaned up all of those I could find.

The application causing the heartburn generates the .exe, appears to run through all of the objects, generates a Warning, and fires a generic error message.  When I close the error message, the 'warning' tab on the build interface disappears, but I can gather the generated .pbd's and the .exe files and run the application.

Is there any way for me to view the save the data on the warning tab to a .text file or something similar, prior to being kicked out of the app?

Thank you,

Kevin

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 2 November 2018 14:38 PM UTC
  2. PowerBuilder
  3. # 4

Hi Kevin;

   FWIW: Before we get into this issue too deep, have you ..

  1. Optimized all your PBL libraries?
  2. Performed a clean full build after optimization with no warnings or errors?
  3. Made sure that your work folder and any sub-folders do not have write protected folders/files?

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.