Another comment: You started to add *_DBG() functions. Here it's called HBIDE_DBG(). But why not use HB_TRACELOG( params ) instead, if you want to force trace calls in live code? F.e. HB_TRACELOG( "hello" )
Anyhow it's much more efficient to use 'HB_TRACE()' since it will be excluded from code for final builds, and not causing any slowdowns because of permanently switched on logging. Some of these may apply to HBXBP and HBQT, I didn't check what is exactly used there. Brgds, Viktor On 2010 Jan 31, at 21:57, Pritpal Bedi wrote: > > Hi All > > Here are the source and .hbi to investigate in deep > what actually is causing increased memory scenario. > > http://n2.nabble.com/file/n4491053/debugmemory.zip debugmemory.zip > > Download this .zip and unzip it in hbide/projects. > Load it in hbIDE and rebuild. You must have Qt environment set. > You may need to change Qt lib location in .hbi. > > To have more traces, change HB_TR_DEBUG calls in QMessageBox.cpp > to HB_TR_ALWAYS and build Qt. > > Then Launch. > > Kepp a watch on memory usage with every invocation of msg box. > > ----- > enjoy hbIDEing... > Pritpal Bedi > _a_student_of_software_analysis_&_design_ > -- > View this message in context: > http://n2.nabble.com/hbQT-c-stub-GC-Some-food-for-thoughts-tp4483724p4491053.html > Sent from the harbour-devel mailing list archive at Nabble.com. > _______________________________________________ > Harbour mailing list (attachment size limit: 40KB) > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
