FiveTech Support Forums

FiveWin / Harbour / xBase community
Board indexAll discussionsLogin (GitHub)
Board index FiveWin for Harbour/xHarbour Another try for using the FWH debugger - some more questions
driessen
Posts: 1467
Joined: Mon Oct 10, 2005 11:26 AM
Another try for using the FWH debugger - some more questions
Posted: Fri Jul 14, 2023 11:41 AM
Hello,

Until now I never had any succes in using the FWH debugger.

This is the MAK-file I use:
Code (fw): Select all Collapse
#Borland make sample, (c) FiveTech Software 2005-2009

HBDIR=c:\software\harbour
BCDIR=c:\progra~1\borland\bcc7
FWDIR=c:\software\fwharb

#change these paths as needed
.path.OBJ = .\obj
.path.PRG = .\
.path.CH  = $(FWDIR)\include;$(HBDIR)\include
.path.C   = .\
.path.RC  = .\

#important: Use Uppercase for filenames extensions, in the next two rules!

PRG =        \
BEHAGEN1.PRG \
BEHAGEN2.PRG \
BEHBOEK1.PRG \
BEHBOEK2.PRG \
BEHDOSS1.PRG \
BEHDOSS2.PRG \
BEHINTRX.PRG \
BEHPAAND.PRG \
BEHPARAM.PRG \
BEHPRARC.PRG \
BEHSOOR1.PRG \
BEHSOOR2.PRG \
BEHUSER.PRG  \
DOCWP1.PRG   \
DOCWP2.PRG   \
FGEGTL1.PRG  \
FGEGTL2.PRG  \
JUDA.PRG     \
MAKEIND.PRG  \
RAPAGPRE.PRG \
RAPDOSBH.PRG \
Z-ERROR1.PRG \
Z-RPREV.PRG  \
Z-WBROWS.PRG

C =        \
BEHAGEN1.C \
BEHAGEN2.C \
BEHBOEK1.C \
BEHBOEK2.C \
BEHDOSS1.C \
BEHDOSS2.C \
BEHINTRX.C \
BEHPAAND.C \
BEHPARAM.C \
BEHPRARC.C \
BEHSOOR1.C \
BEHSOOR2.C \
BEHUSER.C  \
DOCWP1.C   \
DOCWP2.C   \
FGEGTL1.C  \
FGEGTL2.C  \
JUDA.C     \
MAKEIND.C  \
RAPAGPRE.C \
RAPDOSBH.C \
Z-ERROR1.C \
Z-RPREV.C  \
Z-WBROWS.C

OBJ = $(PRGS:.PRG=.\OBJ)
OBJS = $(OBJ:.\=.\obj\)

PROJECT    : JUDA_2.EXE

#RES-file wordt door COMPRES.BAT aangemaakt
#JUDA_2.EXE  : $(PRG:.PRG=.OBJ) $(C:.C=.OBJ) JUDA.RES
JUDA_2.EXE  : $(PRG:.PRG=.OBJ) $(C:.C=.OBJ)
   echo off
   echo $(BCDIR)\lib\c0w32.obj + > b32.bc
#  echo $(OBJS), + >> b32.bc
   echo OBJ\BEHAGEN1.OBJ + >> b32.bc
   echo OBJ\BEHAGEN2.OBJ + >> b32.bc
   echo OBJ\BEHBOEK1.OBJ + >> b32.bc
   echo OBJ\BEHBOEK2.OBJ + >> b32.bc
   echo OBJ\BEHDOSS1.OBJ + >> b32.bc
   echo OBJ\BEHDOSS2.OBJ + >> b32.bc
   echo OBJ\BEHINTRX.OBJ + >> b32.bc
   echo OBJ\BEHPAAND.OBJ + >> b32.bc
   echo OBJ\BEHPARAM.OBJ + >> b32.bc
   echo OBJ\BEHPRARC.OBJ + >> b32.bc
   echo OBJ\BEHSOOR1.OBJ + >> b32.bc
   echo OBJ\BEHSOOR2.OBJ + >> b32.bc
   echo OBJ\BEHUSER.OBJ + >> b32.bc
   echo OBJ\DOCWP1.OBJ + >> b32.bc
   echo OBJ\DOCWP2.OBJ + >> b32.bc
   echo OBJ\FGEGTL1.OBJ + >> b32.bc
   echo OBJ\FGEGTL2.OBJ + >> b32.bc
   echo OBJ\JUDA.OBJ + >> b32.bc
   echo OBJ\MAKEIND.OBJ + >> b32.bc
   echo OBJ\RAPAGPRE.OBJ + >> b32.bc
   echo OBJ\RAPDOSBH.OBJ + >> b32.bc
   echo OBJ\Z-ERROR1.OBJ + >> b32.bc
   echo OBJ\Z-RPREV.OBJ + >> b32.bc
   echo OBJ\Z-WBROWS.OBJ, + >> b32.bc
 
   echo JUDA_2.EXE, + >> b32.bc
   echo JUDA_2.MAP, + >> b32.bc
   echo $(FWDIR)\lib\FiveH.lib $(FWDIR)\lib\FiveHC.lib + >> b32.bc
   echo $(HBDIR)\lib\hbrtl.lib + >> b32.bc
   echo $(HBDIR)\lib\hbvm.lib + >> b32.bc
   echo $(HBDIR)\lib\gtgui.lib + >> b32.bc
   echo $(HBDIR)\lib\hblang.lib + >> b32.bc
   echo $(HBDIR)\lib\hbmacro.lib + >> b32.bc
   echo $(HBDIR)\lib\hbrdd.lib + >> b32.bc
   echo $(HBDIR)\lib\rddntx.lib + >> b32.bc
   echo $(HBDIR)\lib\rddcdx.lib + >> b32.bc
   echo $(HBDIR)\lib\rddfpt.lib + >> b32.bc
   echo $(HBDIR)\lib\hbsix.lib + >> b32.bc
   echo $(HBDIR)\lib\hbdebug.lib + >> b32.bc
   echo $(HBDIR)\lib\hbcommon.lib + >> b32.bc
   echo $(HBDIR)\lib\hbpp.lib + >> b32.bc
   echo $(HBDIR)\lib\hbwin.lib + >> b32.bc
   echo $(HBDIR)\lib\hbcpage.lib + >> b32.bc
   echo $(HBDIR)\lib\hbct.lib + >> b32.bc
   echo $(HBDIR)\lib\png.lib + >> b32.bc
   echo $(HBDIR)\lib\hbcplr.lib + >> b32.bc
   echo $(HBDIR)\lib\xhb.lib + >> b32.bc
   echo $(HBDIR)\lib\hbtip.lib + >> b32.bc
   echo $(HBDIR)\lib\hbzlib.lib + >> b32.bc
   echo $(HBDIR)\lib\hbmzip.lib + >> b32.bc
   echo $(HBDIR)\lib\hbziparc.lib + >> b32.bc
   echo $(HBDIR)\lib\minizip.lib + >> b32.bc
   echo $(HBDIR)\lib\hbpcre.lib + >> b32.bc
   echo $(BCDIR)\lib\cw32.lib + >> b32.bc
   echo $(BCDIR)\lib\uuid.lib + >> b32.bc
   echo $(BCDIR)\lib\import32.lib + >> b32.bc
   echo $(BCDIR)\lib\ws2_32.lib + >> b32.bc
   echo $(BCDIR)\lib\wininet.lib + >> b32.bc
   echo $(BCDIR)\lib\psdk\odbc32.lib + >> b32.bc
   echo $(BCDIR)\lib\psdk\nddeapi.lib + >> b32.bc
   echo $(BCDIR)\lib\psdk\iphlpapi.lib + >> b32.bc
   echo $(BCDIR)\lib\psdk\msimg32.lib + >> b32.bc
   echo $(BCDIR)\lib\psdk\rasapi32.lib + >> b32.bc
   echo $(BCDIR)\lib\psdk\gdiplus.lib + >> b32.bc
   echo $(BCDIR)\lib\psdk\shell32.lib, >> b32.bc

   IF EXIST ..\RES\JUDA.RES echo ..\RES\JUDA.RES >> b32.bc
   $(BCDIR)\bin\ilink32 -Gn -aa -Tpe -s @b32.bc 

.PRG.OBJ:
  $(HBDIR)\bin\harbour $< /N /W0 /V /Oobj\ /I$(FWDIR)\include;$(HBDIR)\include
  $(BCDIR)\bin\bcc32 -c -tWM -I$(HBDIR)\include -oobj\$& obj\$&.c

.C.OBJ:
  echo -c -tWM -D__HARBOUR__ -DHB_API_MACROS > tmp
  echo -I$(HBDIR)\include;$(FWDIR)\include >> tmp
  $(BCDIR)\bin\bcc32 -oobj\$& @tmp $&.c
  del tmp

#RES-file wordt door COMPRES.BAT aangemaakt
#JUDA.RES : ..\RES\JUDA.RC
#  $(BCDIR)\bin\brc32.exe -r ..\RES\JUDA.RC
This MAK-file is working just fine.

But can anyone tell me what changes I have to add to activate the FWH debugger?

Thank you very much in advance for any help.

Regards,

Michel D.
Genk (Belgium)

_____________________________________________________________________________________________

I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773

alerchster
Posts: 137
Joined: Mon Oct 22, 2012 04:43 PM
Re: Another try for using the FWH debugger
Posted: Fri Jul 14, 2023 12:25 PM
add /b in this line
Code (fw): Select all Collapse
$(HBDIR)\bin\harbour $< /N /b /W0 /V /Oobj\ /I$(FWDIR)\include;$(HBDIR)\include
Regards



Ing. Anton Lerchster
driessen
Posts: 1467
Joined: Mon Oct 10, 2005 11:26 AM
Re: Another try for using the FWH debugger
Posted: Fri Jul 14, 2023 12:34 PM

Thank you very much for your help.

Regards,

Michel D.
Genk (Belgium)

_____________________________________________________________________________________________

I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773

driessen
Posts: 1467
Joined: Mon Oct 10, 2005 11:26 AM
Re: Another try for using the FWH debugger - some more questions
Posted: Sat Jul 15, 2023 09:20 AM

Hello,

As told before, I am able know to use the FWH debugger.

Earlier, I used the debugger of xHarbour Builder, but some parts were not working correctly.

To build in a stop, I put "ALTD()" in my source. The debugger stopped automatically at every ALTD().

In the FWH debugger, ALTD() doesn't seem to work.

What can be used in FWH debugger to stop at position where I want it to stop?

Thanks.

Regards,

Michel D.
Genk (Belgium)

_____________________________________________________________________________________________

I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773

Antonio Linares
Posts: 44158
Joined: Thu Oct 06, 2005 05:47 PM
Re: Another try for using the FWH debugger - some more questions
Posted: Sat Jul 15, 2023 04:32 PM

Dear Michel,

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

MsgInfo( "debugger enabled" )

AltD() // Invokes the debugger

MsgInfo( "debugger invoked" )

regards, saludos

Antonio Linares
www.fivetechsoft.com
driessen
Posts: 1467
Joined: Mon Oct 10, 2005 11:26 AM
Re: Another try for using the FWH debugger - some more questions
Posted: Sat Jul 15, 2023 06:27 PM

Fantastic, Antonio.

That is the info I needed.

Regards,

Michel D.
Genk (Belgium)

_____________________________________________________________________________________________

I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773

Marc Venken
Posts: 1487
Joined: Tue Jun 14, 2016 07:51 AM
Re: Another try for using the FWH debugger - some more questions
Posted: Sun Jul 16, 2023 02:13 PM

What is de debugger going to do ? Why use it ?

Marc Venken

Using: FWH 23.08 with Harbour
driessen
Posts: 1467
Joined: Mon Oct 10, 2005 11:26 AM
Re: Another try for using the FWH debugger - some more questions
Posted: Sun Jul 16, 2023 02:37 PM

Mark,

With a debugger, the source is shown while it is executing. It is a very easy utility to help you find a logical error.

Regards,

Michel D.
Genk (Belgium)

_____________________________________________________________________________________________

I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773

Continue the discussion

Static archive · New replies & topics via GitHub Discussions