On Wednesday 02 November 2016 18:01:01 Graeme Geldenhuys wrote:
>
> In fact, I highly recommend you always develop software with the -ghl
> compiler settings defined, and only at building a release do you not
> specify that. Why do I say that? It is much easier to fix a memory leak
> the minute you caused it, than trying to find possibly 100's of them
> months down the line.
>
Agreed. -gh also often shows pointer errors earlier because it fills freed
memory with garbage ("fe") and sets invalid pointers to "deadbeef". So if one
sees the address "deadbeef" in a watch there should ring an alarm bell. ;-)
It also checks the margin of allocated blocks for overwrites.
I too always compile with -ghl while developing.
Martin
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
mseide-msegui-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
