Hello, Thank you for the info.
On Sun, Apr 05, 2015 at 06:38:59PM +0200, Daniel Glöckner wrote: > On Sun, Apr 05, 2015 at 06:16:16PM +0300, Paul Fertser wrote: > > To my surprise, I found that Clang already has the needed facilities > > and they provide awesome diagnostics (with colour highligting): > > > > $ ./configure CC=clang CFLAGS="-fno-omit-frame-pointer \ > > -fsanitize=address -fsanitize=undefined -ggdb3" > > The sanitizers for addresses and undefined behavior (as well as the one > for threads) have already been ported to GCC. They are included since > GCC 4.8 and 4.9 respectively. I was judging by [1] which I assumed was supposed to give accurate information. I specifically wanted "use after return" diagnostics, not "just" address sanitizer. If it works the same for GCC, that's great. [1] https://code.google.com/p/address-sanitizer/wiki/UseAfterReturn -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
