debug breakpoint

[znadie]

I am porting a clipper applicaton to Harbour.
Application runs as in clipper.

There are changes to be made, tried to use debuger.
The following keys do not seem to work,
the run to cursor F7 nothing happens
the set breakpoint F9 no hilite , breakpoint not set

tested enviroment Win7 Pro and XP Pro.

Any hint as to why?

[Dragan Cizmarevic]

Debuger work OK, just must be enabled

Create file hbmk.hbm  and add line with content -b
Or use hmbk2 with option -b
In prg file add line with content ALTD()

Not need cld or something, just start your program, and see debugger like in clipper

[Guillermo Varona Silupú]

Hi Dragan:

The problem is not that no debugger screen appears, the problem is that some functions do not work as indicating znadie.
Me either does not work for example the F7 key to cursor, Breakpoint F9.

BestRegards
GVS

[Przemyslaw Czerpak]

On Mon, 29 Apr 2013, Guillermo Varona Silupú wrote:

Hi,

> The problem is not that no debugger screen appears, the problem is
> that some functions do not work as indicating znadie.
> Me either does not work for example the F7 key to cursor, Breakpoint F9.

Both functions work correctly with Harbour.
But unlike Clipper Harbour knows the lines in which HB_P_LINE pcode
was generated so it does not allow to chose for breakpoints or goto
lines without it. Clipper does not have such information so it allows
to chose any line but of course when wrong line is chosen it cannot
interrupt execution.

best regards,
Przemek

[Guillermo Varona Silupú]

Unfortunately the language barrier does not allow me to clearly
understand the answer.
I have tried F7 and F9 with a small PRG and indeed working properly.
The problem is presented to me in an application with several PRG and
maybe I'm canceling these functions, since within my application
redefine F7 and F9 with SET KEY, however selecting these options do not
work from the main menu of the debugger.

BestRegards
GVS

[znadie]

On Apr 29, 12:32 am, Dragan Cizmarevic <draganc...@gmail.com> wrote:
> Debuger work OK, just must be enabled
>

> Create file hbmk.hbm and add line with content *-b
> *Or use hmbk2 with option* -b
> *In prg file add line with content *ALTD()*

>
> Not need cld or something, just start your program, and see debugger like
> in clipper

using hbide
flags
-gc3
-m
-iD:\hb30\include
-n1
-b
-p

hbide output
----------------------------------------------------------------------------------------------------
Project [ Caja ] Launch [ No ] Rebuild [ No ] Started
[ 17:42:37 ]
----------------------------------------------------------------------------------------------------
Batch File Exists => D:\Temp\52ltbj.bat
Batch File Contents =>
hbmk2 D:\hb30\CAJA\CAJA.hbp -q -trace -info -lang=en -width=512
Command => C:\Windows\system32\cmd.exe
Arguments => /C D:\Temp\52ltbj.bat
----------------------------------------------------------------------------------------------------
CurDir() => Windows\system32 Starting in => D:\hb30\CAJA\

D:\hb30\CAJA>hbmk2 D:\hb30\CAJA\CAJA.hbp -q -trace -info -lang=en -
width=512
hbmk2: Autodetected platform: win
hbmk2: Autodetected C compiler: mingw
hbmk2: Using Harbour: D:\hb30\bin D:\hb30\include D:\hb30\lib\win
\mingw D:\hb30\bin
hbmk2: Using C compiler: D:\hb30\comp\mingw\bin
hbmk2: Harbour compiler command (embedded):
(D:\hb30\bin\harbour.exe) -n2 D:\hb30\CAJA\caja.prg D:\hb30\CAJA
\version.prg D:\hb30\CAJA\rembolso.prg D:\hb30\CAJA\comproba.prg D:
\hb30\CAJA\reports.prg D:\hb30\CAJA\tbutils.prg D:\hb30\CAJA\dict.prg
D:\hb30\CAJA\checkrun.prg D:\hb30\CAJA\CHEKFILE.PRG -gc3 -m -n1 -b -p -
q -oD:\Temp\hbmk_5amunm.dir\ -iD:\hb30\include
Harbour 3.0.0 (Rev. 16951)
Copyright (c) 1999-2011, http://harbour-project.org/

hbmk2: 'cd' to: D:\Temp\hbmk_5amunm.dir
hbmk2: C/C++ compiler command:
D:\hb30\comp\mingw\bin\gcc.exe -c -O3 -march=i586 -mtune=pentiumpro -
fomit-frame-pointer -W -Wall -pipe -ID:/hb30/include D:/Temp/
hbmk_5amunm.dir/caja.c D:/Temp/hbmk_5amunm.dir/version.c D:/Temp/
hbmk_5amunm.dir/rembolso.c D:/Temp/hbmk_5amunm.dir/comproba.c D:/Temp/
hbmk_5amunm.dir/reports.c D:/Temp/hbmk_5amunm.dir/tbutils.c D:/Temp/
hbmk_5amunm.dir/dict.c D:/Temp/hbmk_5amunm.dir/checkrun.c D:/Temp/
hbmk_5amunm.dir/CHEKFILE.c

hbmk2: 'cd' back.
hbmk2: Linking... caja.exe
hbmk2: Linker command:
D:\hb30\comp\mingw\bin\gcc.exe D:/Temp/hbmk_5amunm.dir/caja.o D:/Temp/
hbmk_5amunm.dir/version.o D:/Temp/hbmk_5amunm.dir/rembolso.o D:/Temp/
hbmk_5amunm.dir/comproba.o D:/Temp/hbmk_5amunm.dir/reports.o D:/Temp/
hbmk_5amunm.dir/tbutils.o D:/Temp/hbmk_5amunm.dir/dict.o D:/Temp/
hbmk_5amunm.dir/checkrun.o D:/Temp/hbmk_5amunm.dir/CHEKFILE.o -
mconsole -Wl,--start-group -lhbextern -lhbdebug -lhbvm -lhbrtl -
lhblang -lhbcpage -lgtcgi -lgtpca -lgtstd -lgtwin -lgtwvt -lgtgui -
lhbrdd -lhbuddall -lhbusrrdd -lrddntx -lrddcdx -lrddnsx -lrddfpt -
lhbrdd -lhbhsx -lhbsix -lhbmacro -lhbcplr -lhbpp -lhbcommon -
lhbmainstd -lkernel32 -luser32 -lgdi32 -ladvapi32 -lws2_32 -lwinspool -
lcomctl32 -lcomdlg32 -lshell32 -luuid -lole32 -loleaut32 -lmpr -lwinmm
-lmapi32 -limm32 -lmsimg32 -lwininet -lhbpcre -lhbzlib -Wl,--end-group
-ocaja.exe -LD:/hb30/lib/win/mingw -LD:/hb30/bin

----------------------------------------------------------------------------------------------------
Exit Code [ 0 ] Exit Status [ 0 ] Finished at [ 17:42:41 ] Done in
[ 3.98 Secs ]
--------------------------------------------------------------------------------------------


same code compiled in xHarbour (bcc55) debuger keys work

[znadie]

How does one find the lines?
I get the debugger display but I could not set any breakpoint line in
the program.

I ran the same code by xHarbour with bcc5.1 and the debuger works

I am using HbIDE to compile in Harbour

[znadie]

On Apr 29, 12:32 am, Dragan Cizmarevic <draganc...@gmail.com> wrote:

> Debuger work OK, just must be enabled
>

> Create file hbmk.hbm  and add line with content *-b
> *Or use hmbk2 with option* -b

> *In prg file add line with content *ALTD()*

>
> Not need cld or something, just start your program, and see debugger like
> in clipper

Added altd() to test.prg
compiled with hbmk2 debuger keys work
compiled with hbide debuger keys do not work.
Seems problem is with Hbide