Skip to content

New Tutorial: Know your CFLAGS

Posted by Hanno Böck on
I've lately played a lot with Address Sanitizer, a feature of the gcc and clang compilers that enables additional checks for memory access errors. Surprisingly quite often you don't even have to fuzz an application to find errors, just running it already exposes bugs.

In response to this I wrote a small tutorial describing how Address Sanitizer and other compiler flags can improve software testing and development. I think this is a low hanging fruit measure to improve software quality.

Know your CFLAGS - simple Tips to find Bugs with Compiler Features

Trackbacks

No Trackbacks

Comments

Display comments as Linear | Threaded

Anon on :

What do you think of the extra sanitizer flags described on https://groups.google.com/d/msg/afl-users/2PEEDNpzsx4/cXsjzXI6CAAJ (although I admit a good number of them seem to be on by default in newer sanitizer releases)?

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA

Form options