>> Now I can trace PRG level calls in HBIDE with -D__HB_DEBUG__ define
>> which in turn invokes hb_TraceString( [x] ) which in turn executes
>> hb_tr_trace( HB_TR_ALWAYS,.. ).
>> But still I cannot capture HBQT HB_TRACE( HB_TR_DEBUG, ... ) calls.
>> HBQT compiles and shows up this in log:
>> gc
On Wed, 16 Dec 2009, Pritpal Bedi wrote:
Hi,
> Now I can trace PRG level calls in HBIDE with -D__HB_DEBUG__ define
> which in turn invokes hb_TraceString( [x] ) which in turn executes
> hb_tr_trace( HB_TR_ALWAYS,.. ).
> But still I cannot capture HBQT HB_TRACE( HB_TR_DEBUG, ... ) calls.
> HBQ
Hi
Przemysław Czerpak wrote:
>
> On Wed, 16 Dec 2009, Pritpal Bedi wrote:
> -DHB_TR_LEVEL_* is compile time macro used to strip from source code
> by PP all HB_TRACE() massages which have bigger priority value.
> By default it's set to: HB_TR_LEVEL_WARNING what means that:
>HB_TRACE(HB_TR_A
> I think that it should be replaced by two new functions:
> hb_traceLogLevel( ) ->
> hb_traceLog( ) // generate message at hb_traceLogLevel()
> and we should add also:
> hb_traceLogAt( , )
> which will allow to create PP rules giving the same functionality as we
> have now at C level.
I
On Wed, 16 Dec 2009, Pritpal Bedi wrote:
Hi,
> > First build Harbour without HBQT.
> > Then build HBQT in a separate pass with custom options.
> > Rough instructions for that:
> > ---
> > set HB_WITH_QT=
> > win-make
> > cd contrib/hbqt
> > set HB_WITH_QT=C:\qt\include
> > set HB_USER_CFLAGS=-DTR
>> First build Harbour without HBQT.
>> Then build HBQT in a separate pass with custom options.
>>
>> Rough instructions for that:
>> ---
>> set HB_WITH_QT=
>> win-make
>> cd contrib/hbqt
>> set HB_WITH_QT=C:\qt\include
>> set HB_USER_CFLAGS=-DTR_DEBUG_...
>> set HB_USER_PRGFLAGS=-D__HB_DEBUG__
>>
Hello Viktor
Viktor Szakáts wrote:
>
> First build Harbour without HBQT.
> Then build HBQT in a separate pass with custom options.
>
> Rough instructions for that:
> ---
> set HB_WITH_QT=
> win-make
> cd contrib/hbqt
> set HB_WITH_QT=C:\qt\include
> set HB_USER_CFLAGS=-DTR_DEBUG_...
> set HB_U
Hi Pritpal,
First build Harbour without HBQT.
Then build HBQT in a separate pass with custom options.
Rough instructions for that:
---
set HB_WITH_QT=
win-make
cd contrib/hbqt
set HB_WITH_QT=C:\qt\include
set HB_USER_CFLAGS=-DTR_DEBUG_...
set HB_USER_PRGFLAGS=-D__HB_DEBUG__
win-make
cd ../..
---
Hello All,
As per subject.
Goal is to trace calls for only the part I am
interested in. I do not want entire application tracing.
I have tried my level best but am not been successful.
Regards
Pritpal Bedi
--
View this message in context:
http://old.nabble.com/HB_TRACE%28%29---How-to-invok
On Fri, 31 Oct 2008, Pritpal Bedi wrote:
Hi Pritpal,
> How can I invoke
> HB_TRACE( HB_TR_DEBUG, ( "hb_gt_wvt_Redraw(%p,%d,%d,%d)", pGT, iRow, iCol,
> iSize ) );
> to work ?
read doc/tracing.txt
Short instruction. Compile the code you want to trace with
HB_TR_LEVEL_DEBUG macro, f.e.:
set C_
Hello Folks
Please do not laugh at my stupidity.
How can I invoke
HB_TRACE( HB_TR_DEBUG, ( "hb_gt_wvt_Redraw(%p,%d,%d,%d)", pGT, iRow, iCol,
iSize ) );
to work ?
Also can this debug output be directed to outer debug engines,
I mean same as I can achieve with hb_ToOutDebug() function ?
Regard
11 matches
Mail list logo
