1. Mary Jane Foster
  2. PowerBuilder
  3. Wednesday, 6 November 2024 17:37 PM UTC

Hi:

In PowerBuilder 2022 R3, we are experiencing an issue with the PBAutoBuild220.exe. The build is failing and we get a build log, but it does not write to the build error log.  Here is the command:

PBAutoBuild220.exe /f "App.json" /l BuildLog.log /le BuildErrLog.log

I do not know if the following in formation is relevant, but offering it up:

  • It is one developer, two branches, and it is happening after a rebase and push.  The only change in those branches are the rebase - all prior pushes built successfully.
  • Our build succeeds if we do a manual build in the IDE sometimes, and sometimes it just crashes, thus no error log.  It clones successfully, from the IDE, Sourcetree, bash.   
  • The only information we have is the build log, and it never fails in the same place, yay!  Not. 
  • Two weeks ago, we experienced the same thing on the same branch, always after a rebase, we wound up making one change at a time, and found the line of code (it wasn't bad) that caused it to fail.  We moved a function and voila, all was good.  This is time consuming.
  • Without any error (log or otherwise) to give us any hint as to what the issue is, it is like playing where's waldo without the book.
  • Never experienced this with PB 2021.

Questions:

  • Why am I not getting an error log?  According to your documentation, PBAutoBuild220.exe "has different compilation logic and uses different compilation methods from PowerBuilder IDE. Moreover, it has more internal detections and error correction functions..."  It would be great if those internal detections were offered up in a log file.
  • Does anyone have any suggestions on how to narrow down the issue when I have yet to get an error log?
  • Can it be a dependency issue?  Is it possible I need to look at the target sequence?  Please note, this same sequence has been in play for 20+ years and we haven't introduced a new .pbl for more than 10.

All suggestions appreciated.

MJ

 

Mary Jane Foster Accepted Answer Pending Moderation
  1. Monday, 11 November 2024 20:11 PM UTC
  2. PowerBuilder
  3. # 1

I found the .dmp files from the failures within the IDE.  Using Windlg I am seeing the common access violation due to a bitness mismatch.  This is my first experience with Windlg and here are the basic things I've found:

Key : Failure.Bucket
Value: BITNESS_MISMATCH_X86_NULL_POINTER_WRITE_c0000005_pbshr.dll!Unknown

Key : Failure.Hash
Value: {2ab4ded3-1615-df4f-22f3-393f05a6d63a}

PROCESS_NAME: PB220.exe

WRITE_ADDRESS: 00000000

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 00000000

In PB 2021 we converted to running our application as 64 bit and when we upgraded to PB 2022 (a year ago +-), after reading the migration steps, we did a deeper dive and made some additional changes and we've only recently begun to experience this issue.  I'm struggling with how to find the offending code, and I have some questions:

  1. Can you give me an tips/tricks to look through the .dmp file (or my source code) that will help me identify where the error is occurring?
  2. Is it possible a library has just hit an  object number/size threshold?  These particular libraries are larger than they should be according to a forum post I read over the weekend.

I've attached a zip of the .dmp file for you.  

I'm still trying to find some kind of .dmp file or error log from the PBAutoBuild220.exe runs.

In the meantime, we have commented all new code out and are introducing it one hunk at a time in hopes that we can narrow it down that way.

Thank you.

MJ

 

Attachments (1)
Comment
There are no comments made yet.
Mary Jane Foster Accepted Answer Pending Moderation
  1. Friday, 8 November 2024 13:43 PM UTC
  2. PowerBuilder
  3. # 2

Hi Chris:

The update did not help me.  It is still failing and I am not getting any error messages.

Are there logs anywhere?  It just crashes and I am getting nowhere.  Are there any dump files created that I can find and dig through?

Again, I'm open to all suggestions.  

MJ

Comment
  1. Chris Pollach @Appeon
  2. Friday, 8 November 2024 15:56 PM UTC
Hi MJ;

Thank for trying the latest MR build. Sorry that this did not fix your issue. For the PBAutoBuil utility, you can specify various logging options in the command line arguments. If the IDE crashes, there should be a mini-crash dump in the O/S Application Event log.

If this issue is not found on other PB developer machines in your organization, then I would look for what is different about your machine / OS / configuration, etc compared to the one(s) that are working. If other PB developers are also encountering these issues, then I would suggest that you gather both the PBAutoBuild logs and IDE dump information (as suggested above) & then open a Support Ticket for this problem. https://www.appeon.com/standardsupport

Regards .. Chris
  1. Helpful
  1. Mary Jane Foster
  2. Friday, 15 November 2024 20:35 PM UTC
Hi Chris:

As requested a ticket has been opened to figure out the error and to get the compiler to report the errors. In the meantime, we continue on our end to look into this. It looks and feels like a compiler issue and I would like to understand more about it. It doesn't always fail in the same spot, but sometimes it fails when it says "Creating Compilation List". Can you tell me how it creates this list? I'm grasping at straws looking for any pattern(s).

At one point we commented out all the developer's code and re-introduced it one statement block at a time, and compiled and found the last thing we put back in , it failed. It was a commit. We moved a destroy, and compiled it worked. It made no sense. We put everything back in its original place, including the commit, and it compiled fine. Thus a lot of building and regenerating, and magically it somehow worked. But we can't trust it. It is the exact same code, I've compared it to the object we weren't manipulating at all (thank you Git). At this point we don't trust it though because we are afraid it will happen with the next rebase and maybe introducing a problem to other developers. Can you tell me how moving code around and constant compiling and building and putting the code back in its original place could impact it?



Any and all thoughts to help me understand how the compiler works is appreciated.







  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 15 November 2024 21:06 PM UTC
The main Support Team should be able to help you now through this issue. ;-)
  1. Helpful
There are no comments made yet.
Mary Jane Foster Accepted Answer Pending Moderation
  1. Wednesday, 6 November 2024 19:04 PM UTC
  2. PowerBuilder
  3. # 3

Hi Chris:

No, we are on 3289.  I am working on completing the upgrade to our other suite of applications before upgrading again.  Unless I absolutely have to.

Thank you for the quick response.

MJ

Comment
  1. Chris Pollach @Appeon
  2. Wednesday, 6 November 2024 19:23 PM UTC
Hi MJ;

FYI:there have been fixes to the PBAutoBuild in later builds than yours. For example ...

https://www.appeon.com/standardsupport/bugfixes/view?id=1241

https://www.appeon.com/standardsupport/bugfixes/view?id=1161

I am not sure if these later builds might address your issue. You would have to try.

Food for thought.

Regards .. Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 6 November 2024 18:52 PM UTC
  2. PowerBuilder
  3. # 4

Hi MJ;

  Are you using one of the latest builds of R3 (3391 or 3397)?

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.