Xavi-2 wrote:
>
> Don't change the existing but new or 3-prt libraries can take advantage of
> this.
> Also, perhaps in the future, the macro can be extended to other checks and
> the code is not more difficult than HB_TRACE.
>
Are you saying that using this macro in required source will be enough?
If yes, my vote is yes. Better if it is one line but formatted like a
record.
Here is what I suggest:
> Total memory allocated: 234123 bytes (4176 block(s))
> Warning, memory allocated but not released: 1020 bytes (2 block(s))
> Block 1 0xd88970 (size 200) MYFUNCTION(256), "200F200F ..."
> myfile.c:256 [ char *pPtr = (char *)hb_xgrab( size ) ]
> Block 2 0xe4a990 (size 200) QT_QTEXTDECODER(129), "200F200F ..."
> qtcore.cpp:129 [ pObj = ( QTextDecoder* ) new QTextDecoder(
> hbqt_par_QTextCodec( 1 ) ) ]
>
Block 0001 0xde88970 (size 00200) MYFUNCTION(256) myfile.c:256 [
char *pPtr = (char *)hb_xgrab( size ) ]
^^^^^^^^^^^^^
^^^^^^^
^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^....
One line per block.
Fixed Length every field except last.
Memory dump be optional and at the end ( formatted to fixed length ).
I find existing implementation difficult to follow especially in large logs.
-----
enjoy hbIDEing...
Pritpal Bedi
_a_student_of_software_analysis_&_design_
--
View this message in context:
http://n2.nabble.com/Extented-FM-Stats-with-new-trace-macro-HB-TRFM-tp4489774p4490105.html
Sent from the harbour-devel mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
