Some problems with the FWH-debugger

[driessen]

Hello everyone,

I'm trying to use the FWH-debugger, but like it is now, it is to my opinion unuseable.

Some problems I experience:

1. ALTD(), ALTD(0), ALTD(1) - all the commands aren't working at all. There is no reaction from the debugger when using one of them.
2. A lot of words in windows, menues, etc. are in Spanish. Very difficult for someone who is not speaking one single word of Spanish.
3. How to open another PRG-file to toggle breakpoints? If that was possible, that would be a very big forward. Sorry, but I can't find it.

If these problems could be solved, the FWH-debugger would be a very helpful tool.

I'm using the xHarbour debugger right now, but this one is also has its problems. Unfortunately, I don't see any evolution anymore in xHarbour (no change for the last 3 years at all), so I want to stop using it.

Thank you very much for any comment of help.

[Enrico Maria Giordano]

I'm using the xHarbour debugger right now, but this one is also has its problems. Unfortunately, I don't see any evolution anymore in xHarbour (no change for the last 3 years at all), so I want to stop using it.

This is not true, at least for the official xHarbour.org compiler:

https://github.com/ronpinkas/xharbour/b ... /ChangeLog

[driessen]

Sorry, Enrico, I have always been using the xHarbour which of xHarbour.com.
This xHarbour versionn which wasn't free, hasn't been updated since build 772 of 2020, meanwhile 3 years ago.
To my opinion, that is not were I am paying for every six months.

Can I change to xHarbour.org? If so, what do I need to do?

Thanks.

[Antonio Linares]

Dear Michel,

Please go to FWH\samples and run this:

buildh tutor01 -b

The debugger shows and works fine. Please try it and let me know what you get

many thanks

[frose]

Michel,
use the "Paperclip" in the toolbar to open other PRG files.
Otherwise you are right, especially that AltD() does not work.
Also the debugger is quite slow due to its data structure.

[driessen]

Antonio,

The debugger is working. I get the debug screen. The problem is that de debugger doesn't stop were I want it to stop.
When I put ALTD() in my PRG, nothing happens.

Thanks.

[Antonio Linares]

Dear Michel,

We provide this example in FWH\samples

altd.prg

Code: Select all | Expand

// Sample showing how to invoke the console debugger from Harbour/xHarbour
// Notice you have to compile it using /b
// and remove -aa when calling ilink32.exe from buildh.bat/buildx.bat

REQUEST HB_GT_WIN 
REQUEST HB_GT_WIN_DEFAULT

function Main()

   AltD( 1 )   // Enables the debugger. Press F5 to go

   MsgInfo( "debugger enabled" )

   AltD()      // Invokes the debugger

   MsgInfo( "debugger invoked" )

return nil

// Harbour requirement
procedure hb_gt_gui_default 
return

[driessen]

Antonio,

Unfortunately, I get this error while building my application.

Code: Select all | Expand

Error: Unresolved external '_HB_FUN_HB_GT_WIN' referenced from OBJ\JUDA.OBJ
Error: Unresolved external '_HB_FUN_HB_GT_WIN_DEFAULT' referenced from OBJ\JUDA.OBJ
Error: Unable to perform link

Any idea?

Thanks.

[Enrico Maria Giordano]

Sorry, Enrico, I have always been using the xHarbour which of xHarbour.com.
This xHarbour versionn which wasn't free, hasn't been updated since build 772 of 2020, meanwhile 3 years ago.
To my opinion, that is not were I am paying for every six months.

Yes, I agree: xHarbour.com is a dead company and I am very sorry for that.

Can I change to xHarbour.org? If so, what do I need to do?

Please visit www.xharbour.org and download the C compiler (I recommend MSVC) and the corresponding xHarbour binaries. For any help I'm here.

[Enrico Maria Giordano]

Antonio,

Unfortunately, I get this error while building my application.

Code: Select all | Expand

Error: Unresolved external '_HB_FUN_HB_GT_WIN' referenced from OBJ\JUDA.OBJ
Error: Unresolved external '_HB_FUN_HB_GT_WIN_DEFAULT' referenced from OBJ\JUDA.OBJ
Error: Unable to perform link

Any idea?

Thanks.

Try to remove them. I think they are for Harbour not for xHarbour.

[driessen]

Enrico,

Thanks for your reply.

But also in Harbour, I got the same error.

[Antonio Linares]

Dear Michel,

debugging an event driven environment is not easy. Better use traces instead of a debugger