Hi!
----
Below is a valgrind hit found with valgrinds's stack check tool
("exp-sgcheck" - this tool checks stack+static variables... the
previous reports about valgrind issues were done with the heap checker
called "memcheck").
After some hours of checking we only found one hit in ast-ksh.2012-05-18:
-- snip --
$ valgrind --tool=exp-sgcheck --trace-children=yes --read-var-info=yes
--num-callers=50 ...
[snip]
==15591== Invalid read of size 1
==15591== at 0x548B49: sfvprintf (sfvprintf.c:755)
==15591== by 0x53C4EB: sfvsprintf (sfprintf.c:75)
==15591== by 0x53C625: sfsprintf (sfprintf.c:115)
==15591== by 0x4DF165: _ast_pathtemp (pathtemp.c:322)
==15591== by 0x5453F2: _tmpfd (sftmp.c:210)
==15591== by 0x5455BD: _tmpexcept (sftmp.c:311)
==15591== by 0x535DE5: sfdisc (sfdisc.c:203)
==15591== by 0x478D17: sh_subtmpfile (subshell.c:124)
==15591== by 0x482213: sh_exec (xec.c:1575)
==15591== by 0x47A5B2: sh_subshell (subshell.c:583)
==15591== by 0x456516: comsubst (macro.c:2132)
==15591== by 0x452202: varsub (macro.c:1163)
==15591== by 0x450777: copyto (macro.c:633)
==15591== by 0x44EF32: sh_macexpand (macro.c:246)
==15591== by 0x44FB97: sh_macpat (macro.c:424)
==15591== by 0x486909: sh_exec (xec.c:2824)
==15591== by 0x485646: sh_exec (xec.c:2493)
==15591== by 0x418956: exfile (main.c:600)
==15591== by 0x417B40: sh_main (main.c:373)
==15591== by 0x416C28: main (pmain.c:45)
==15591== Address 0x7feffdbe8 expected vs actual:
==15591== Expected: unknown
==15591== Actual: stack array "keybuf" of size 16 in frame 3 back from here
-- snip --
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [email protected]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 3992797
(;O/ \/ \O;)
_______________________________________________
ast-developers mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/ast-developers
