<div dir="ltr">Just a remark, as some people asked me about it privately.<div>I'm not interested in static analysis (which gcc gives for uninitialized variables). But with runtime analysis of where the uninitialized variable have been actually used when the code was run. This is useful in many situations (for instance, when having 3000 (literally) static warnings, some of similar spirit, and no time to check them all)</div>
<div>I didn't find anything parallel to that for gcc.</div><div><br><div class="gmail_quote">On Mon, Jan 11, 2010 at 11:54 PM, Elazar Leibovich <span dir="ltr"><<a href="mailto:elazarl@gmail.com">elazarl@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">We have a big legacy embedded code we need to maintain. Often, we wish to run some functions of the code on the PC with injected input, to test them or to test changes we've done to them without loading the code to the device it should run on.<div>
The code is written with C.<br><div>Obviously, this is not an easy task, it is more difficult because, the code is bug ridden, and many times it works by accident (for example, a NULL pointer added a constant and then derefeced, this worked because the memory address was legal).</div>
<div>Since the code is big, our strategy is: compile just the parts you need, debug it enough so that it would run on the PC, and keep the changes. Hopefully, after enough time, all (or most) of the code would be runnable on a PC.</div>
<div>We use gcc+gdb to compile and debug the code. In Visual Studio's cl.exe there are some <a href="http://msdn.microsoft.com/en-us/library/aa289171(VS.71).aspx" target="_blank">security checks</a> at run time. This can really assist debugging. For example knowing when an unintialized variable was used can save you alot of frustration when trying to figure out why you're getting a wrong numberic results.</div>
<div>My questions are:</div><div>1) Are there parallel (or better) runtime security checks for gcc/gdb? I found the -fstack-protection stack canary switch, but are there more of this type?</div><div>2) What other tools are there which offer similar protection? Valgrind of course is the first thing that comes to my mind, but I'll be glad to hear any more ideas.</div>
<div>For example, I would love to be able to get a warning whenever a pointer is dereferenced twice, where the first time the pointer points at the memory address of variable x, and the second time it points to variable y. That way I'll get a warning for the following bug:</div>
<div>int x[3] = {1,2,3};int y[3] = {4,5,6};</div><div>int *p = x;</div><div>for (int i=0;i<=3;i++,p++) (*p) = (*p)++; // note the <=</div><div>3) We use win32 for regular development, so if anyone knows what is the support for such tests in cygwin/mingw, I'll be glad to hear about it.</div>
<div><br></div><div>Thanks</div><div>Elazar Leibovich</div></div></div>
</blockquote></div><br></div></div>