1. Géza Bartha
  2. PowerBuilder
  3. Monday, 29 July 2019 13:49 PM UTC

Dear Support!

Sometimes, my program crashes. How to find where is the issue? There is no error message, but the program was shutdown.

Please help to us! Offer some debugger, or any kind of solution. 

Bye, Geza.

 

 

 

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 29 July 2019 17:38 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Geza;

   FWIW: I would first look in the MS-Window "Event Logs" for related information about your App's crash.

Regards ... Chris

Comment
There are no comments made yet.
Michael Kramer Accepted Answer Pending Moderation
  1. Monday, 29 July 2019 15:03 PM UTC
  2. PowerBuilder
  3. # 1

Hi Geza, questions:

  • Do you have no error message on screen?
  • Do you have steps to repro?
  • PB version/build?
  • O/S version?

Well, very little concrete to offer without details.

Have you tried to reproduce error running PowerBuilder's built-in Debugger?

If it only occurs runtime and it simple crashes hard without any info on screen => Consider running with /PBDEBUG enabled to capture log indicating exact spot where app crashes.

WARNING - /PBDEBUG: Performance degrades, log file is huge, and disk space is therefore consumed fast. Only use /PBDEBUG when really needed.

HTH /Michael

 

Comment
  1. Tobias Roth
  2. Wednesday, 31 July 2019 12:39 PM UTC
The dbg-file of PBDEBUG-Mode is quite large and not so good to read.

There is an tool, called PBL-Peeper, to read that file. It works fine with PB9 - PB2017R3 (I think PB2019 should work too)

You can download the tool here: http://www.techno-kitten.com/PBL_Peeper/Download/download.html



You can open the generated dbg-file and a pbt-file to scroll through every executed line of code.



1. Open a PBT-File at TabPage PBLs

2. Select the dbg-file at Tabpage Trace



Result:

On the left side is a treeview that displays the DBG-File.

On the right side is the source code of the selected tree-item.
  1. Helpful
  1. Géza Bartha
  2. Wednesday, 31 July 2019 18:26 PM UTC
I'm sorry. I missed your comment.

The /pbdebug is impossible in my customers, because the program speed changes to very slow with /pbdebug, and my partners immediately scream for us, why slow, why they cannot work, and they complain your boss, who complains my boss, who stops the experiment. The show must go on :(

  1. Helpful
There are no comments made yet.
Géza Bartha Accepted Answer Pending Moderation
  1. Tuesday, 30 July 2019 07:08 AM UTC
  2. PowerBuilder
  3. # 2

Dear Support!

Sorry, but I'm not speaking very good in English, sorry for my mistakes.

My program very old, but this crash have got in older versions of powerbuilder as well. The visual studio can catch the exception of older version of powerbuilder (10.5.2 several build, we are trying 11.5, 12.5, and now 17 versions, but this error have no solution) We are try several OS, for example, XP (the older version of powerbuilder), and windows 7, windows 8, and windows 10 as well.

The exception
pbdwe105.dll

in dwControlStyleDlgProc function

I think it is memory overflow, But the crash exception of powerbuilder 2017 cannot catch the old version of Visual studio (2008).

The event log from my computer:

Windows 10 Pro

-
-

1002
2
101
0x80000000000000

1446
Application
mcemer014.matrix2.meditcom.hu


-
PB170.EXE
17.2.0.1880
1170
01d53e385ae1632f
37
C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE
0b22ca81-085e-4ef4-ba17-7dafa093154b


55006E006B006E006F0077006E0000000000



-------------------------------------------------------------------------------------------------------------

-
-

1002
2
101
0x80000000000000

2223
Application
mcemer014.matrix2.meditcom.hu


-
PB170.EXE
17.2.0.1880
1fd8
01d545e9898d8004
41
C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE
b3d7d14b-8039-4572-8555-b9a2258a0cd8


55006E006B006E006F0077006E0000000000



-------------------------------------------------------------------------------------------------------------

And we are waiting my customers' machines event logs now. They promise tomorrow. Sorry.

Comment
There are no comments made yet.
Géza Bartha Accepted Answer Pending Moderation
  1. Tuesday, 30 July 2019 07:17 AM UTC
  2. PowerBuilder
  3. # 3
- 
- 
   
  1002 
  2 
  101 
  0x80000000000000 
   
  1446 
  Application 
  mcemer014.matrix2.meditcom.hu 
   
  
- 
  PB170.EXE 
  17.2.0.1880 
  1170 
  01d53e385ae1632f 
  37 
  C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE 
  0b22ca81-085e-4ef4-ba17-7dafa093154b 
   
   
  55006E006B006E006F0077006E0000000000 
  
  
  
  -------------------------------------------------------------------------------------------------------------
  
  - 
- 
   
  1002 
  2 
  101 
  0x80000000000000 
   
  2223 
  Application 
  mcemer014.matrix2.meditcom.hu 
   
  
- 
  PB170.EXE 
  17.2.0.1880 
  1fd8 
  01d545e9898d8004 
  41 
  C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE 
  b3d7d14b-8039-4572-8555-b9a2258a0cd8 
   
   
  55006E006B006E006F0077006E0000000000 
  
  
  
  -------------------------------------------------------------------------------------------------------------

 

For better readable.

Comment
There are no comments made yet.
Géza Bartha Accepted Answer Pending Moderation
  1. Tuesday, 30 July 2019 07:18 AM UTC
  2. PowerBuilder
  3. # 4

The xml is not attachable, and not viewable :(.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 30 July 2019 15:28 PM UTC
  2. PowerBuilder
  3. # 5

Hi Géza ;

    It sounds like this issue is also reproducible in many PB versions from your current 10.5.2 through to the almost end of the Sybase versions 12.5.x. So it sounds like your application might be the source of all your woes.

    Can you tell us ...

1) Have you run the Migration Assistant in a higher PB IDE version against your old PB 10.x App's source code to if possible coding issues exist before you migrate?

2) If you perform a Full Build ... is the compilation clean (no warnings or errors)?

3) Have you tried optimizing all your PBL's?

Regards ... Chris

Comment
There are no comments made yet.
Géza Bartha Accepted Answer Pending Moderation
  1. Wednesday, 31 July 2019 09:11 AM UTC
  2. PowerBuilder
  3. # 6

Hi Chris!

 

Thanks for your help.

 

1) Have you run the Migration Assistant in a higher PB IDE version against your old PB 10.x App's source code to if possible coding issues exist before you migrate? 

NO, but I've tried now the previous source and got a lot notification. We are going to verify, but the most of notification is environment.pbmajorrevision, or monitor screen width and height or This match may be valid PowerScript syntax, but also matches an identifier in the search file. 

The second case for example in function

public function integer of_parsepath (string as_path, ref string as_out_dir, ref string as_out_file);
Long li_pos
li_pos = Pos(Reverse(as_path), "\")
If li_pos > 0 Then
as_out_dir = Left(as_path, Len(as_path) - li_pos)
as_out_file = Right(as_path, li_pos - 1)
Else
as_out_file = as_path
as_out_dir = ""
End If

Return 1
end function

 How to resolve they?

  

2) If you perform a Full Build ... is the compilation clean (no warnings or errors)?

No error, but there are a lot of warning, we will try to explode them.

3) Have you tried optimizing all your PBL's?

No, but we will optimize all pbl.

 

 

Regards, Géza

 

 

 

Comment
  1. Michael Kramer
  2. Wednesday, 31 July 2019 15:21 PM UTC
The highlighted code line and the following THEN-clause is similar to using LastPos(as_path, "\") to split filename from path. Maybe a more descriptive name for this function is of_SplitFullPathNameIntoPathAndFile(…).
  1. Helpful
  1. Michael Kramer
  2. Wednesday, 31 July 2019 15:27 PM UTC
Q1 :: Do you see crash also when running your app using PowerBuilder IDE's Debugger?

If you do, you should be able to pinpoint the code where crash appears.

Breakpoint just before crash can tell you call stack, objects in memory, property/variable values, etc.

Q2 :: Using Task Manager or any other tool what are characteristics of your app just before the crash: allocated memory, handle count, cpu %, etc?

Out-of-memory condition or other resource starvation should be visible before crash appears.
  1. Helpful
  1. Géza Bartha
  2. Wednesday, 31 July 2019 18:44 PM UTC
This is a part of bought component. Not is our name convention. But the question is how to rewrite,the migration assistant doesn''t have to complain for this function.



Q1> I see the crash hardly ever. But my customers work a lot of our software, and they work a lot of machine (100+) and they see crash more often. And i don't know which part of script crashed, to put the breakpoint,and i can see the circumstances.



Q2> The crash is not predictable now. The "before" is not definable.



We would like to localise, which parts of script are bad, but the "event" is not predictable :(
  1. Helpful
There are no comments made yet.
Géza Bartha Accepted Answer Pending Moderation
  1. Monday, 12 August 2019 07:26 AM UTC
  2. PowerBuilder
  3. # 7

I think, the problem is another pbvm170.dll. We've installed the R3 1880, but the runtime use earlier version of pbvm170.dll, because it found another directory. After we deleted all earlier versions of runtime dlls, the number of crash significant lower.

 

We want to apply all of your offerings, but the remove of warnings is impossible.

The webservice has got inheritance, when i have generated object stub, the superclass variables are showing in the inherited class variables next to, but this inherited variables appear than own variable (redefine super variable), in the server of webservice these variables defined only the parent (super) class.

 

 

class A {

int x;

}

 

class B inherited from class A (

  int f;

}

B.f = 1 is possible, because its owner variable

B.x = 1 is possible, because the super class of variable

But the .NET webservice generate definition of x varisable in the b class, they appears owner variables, after we get warnings.

 

 

 

 

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.