Hi
More deeper analysis revealed that multiple freeing of
pointers is triggered if an invalid pointer is sent to hb_xfree().
Like this:
delete ( ( QWidget * ) p->ph );
delete p->ph; // this triggers multiple freeing
So the test scenario I presented is wrong altogether.
only
delete ( ( QWidget * ) p->ph );
is enough and operator in our stub is called.
Good news is that hbXBP/demoxbp.exe stays almost
on the same level of memory usage, the phenomena hogging
me all the time.
The bad news is, for some delete calls our operator is never
reached, especially after application exit, and fm log reports
unreleased memory block.
Still under test scenario, will update if I could find anything useful.
Viktor, is not it a good idea to put this stub in hbqt.lib itself ?
-----
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-tp4483724p4485725.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
