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

Resolved Need External Debugger for PB 2019 R3

  1. Advice
0
Votes
Undo
  1. himanshi tayal
    himanshi tayal
  2. PowerBuilder
  3. Thursday, 5 September 2024 08:58 AM UTC

Hello ,

We are working on Appeon 2019 R3 version 64 bit but here problem is that debugger is not working as IDE is still on 32 bitand we hve external dll which move to 64 bit.

Do we have any external debugger which we can use to debug the code and find issues in the code as we are getting NULL pointer in one of the window and we are not able to find the exact function i.e from where it is coming ?

Problem with LenA function when migrating to PB19
PVBM.DLL cannot be loaded from C++
Responses (3)
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Friday, 6 September 2024 14:32 PM UTC
  2. PowerBuilder
  3. # 1

You can try to start your exe with the /pbdebug option.

But be warned. This can be really slow.

https://docs.appeon.com/pb2019/pbug/ch33s08.html

hth

Arnd

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 6 September 2024 14:08 PM UTC
  2. PowerBuilder
  3. # 2

Add this as a global external function:

Subroutine OutputDebugString( &
	string lpOutputString &
	) Library "kernel32.dll" Alias For "OutputDebugStringW"

Then go here and download the DebugView app:

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

You can add calls to OutputDebugString in your code. The string will appear in the DebugView app.

Comment
himanshi tayal
  1. himanshi tayal
  2. Monday, 9 September 2024 13:34 PM UTC
It is same as Messagebox("Information" ,"We are here")



I want such debugger which works same as internal debugger , trace every existing functions , shows which function , user object is invoking.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Monday, 9 September 2024 13:57 PM UTC
You'll have to follow Andreas' suggestion. Install PB 2022-R3, make a copy of your workspace, open the copy in PB 2022-R3, and run the debugger in 64-bit mode.
  1. Helpful 3
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Tuesday, 10 September 2024 12:45 PM UTC
I agree with Andreas & Roland
  1. Helpful
There are no comments made yet.
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Thursday, 5 September 2024 09:11 AM UTC
  2. PowerBuilder
  3. # 3

Hi.

The simplest thing I can think is to take a copy of the project, migrate it to 2022 R3, and check if the specific issue occurs there. If yes, then debug using 2022 R3 to see what is causing the problem...

Andreas.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 6 September 2024 01:04 AM UTC
Adding to what Andreas said, PB 2022 R3 has a 64-bit debugger whereas PB 2019 R3 does not.
  1. Helpful 1
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.