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

Resolved Changed debugging behaviour in PB 2017 R2 ???

  1. Issue
0
Votes
Undo
  1. Martin Kaltenböck
    Martin Kaltenböck
  2. PowerBuilder
  3. Tuesday, 27 February 2018 08:52 AM UTC

I just started to do my first steps in PB 2017 R2.

I migrated a small application from PB 12.1 to PB 2017 R2 without any problems.

Now I noticed a behaviour change in debugging my code.

I usually use the debugbreak() - function to set the breakpoint and debug from this position.

Procedure in PB 12.1:

- Run application with Run-Button

- Execution stops at debugbreak()

- Used Step In / Step Over and so on to debug

Procedure in PB 2017 R2:

- Run application with Run-Button

- Execution stops at debugbreak()

- BUT NOW: if i click 'Step Over' or 'Step In' the execution is continued (as I would have clicked 'Continue')     (<---- this is the error / my question)

 

Then I tried this in PB 2017 R2:

- Start the application with Debug-Button

- Application 'waits' in the application open()-event

- Click Start-Button

- Execution stops as debugbreak()

- Now Step Over / Step In works.

 

Did anyone else run into this issue?

 

Of course, there is only one click more in the new behaviour, but I would be happy with the old one ...

Thank you for reply

Martin

 

  1. Bug
"Potential" Show stopper for 2017R2 - FIX NEEDED A...
C# function calling in Powerbuilder 2017 R2
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 27 February 2018 15:57 PM UTC
  2. PowerBuilder
  3. # 1

Hi Martin;

  I could could not replicate your described behaviour in PB 2017 R2 build 1756. Once I hit a break point or use the "Just in time" debugging option, I can step over or into code without any issues on any PowerScript one line at a time, as follows:

Note: I am using the Fall Creator edition of W10 - version 10.0.0.16299.

Regards ... Chris

Comment
Martin Kaltenböck
  1. Martin Kaltenböck
  2. Tuesday, 27 February 2018 18:58 PM UTC
Hi Chris,



and did you start the session with the Run- or the Debug-Button?



BTW, I did my tests here on a Windows 7 machine ...



 

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 28 February 2018 15:19 PM UTC
Using the DEBUG button. I can also use the "Just in time Debugging" feature as well.

  1. Helpful
There are no comments made yet.
Brad Wery
Brad Wery Accepted Answer Pending Moderation
  1. Wednesday, 28 February 2018 17:43 PM UTC
  2. PowerBuilder
  3. # 2

I tested in PB12.6 and it's an issue there as well. Looks like it's a bug that Appeon inherited from SAP. You'll probably have to log this one.

As Chris noted, using the debug button to run the application works.

Comment
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Thursday, 1 March 2018 07:11 AM UTC
  2. PowerBuilder
  3. # 3

Hi Martin,

Thanks for reporting this problem! We reproduced it on our end and will do further research to figure it out. We will keep you posted about the progress.

BTW, PB 12.6 has the same issue.

 

Regards... Ken

 

 

Comment
Martin Kaltenböck
  1. Martin Kaltenböck
  2. Thursday, 1 March 2018 19:16 PM UTC
Thank you, nice to know!

  1. Helpful
Alfredo Aldama
  1. Alfredo Aldama
  2. Sunday, 1 April 2018 02:18 AM UTC
Hi,



I could  replicate your described behaviour in PB 2017 R2 build 1756, i use -> debugbreak() and then press F8 



Regards !



 

  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.