[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 243234] ptrcheck doesnt handle sscanf properly
From:       Lars Kr. Lundin <kde () lklundin ! dk>
Date:       2013-11-03 18:53:24
Message-ID: bug-243234-17878-Fns3saoV4q () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=243234

Lars Kr. Lundin <kde@lklundin.dk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kde@lklundin.dk

--- Comment #6 from Lars Kr. Lundin <kde@lklundin.dk> ---
Similar to the write warning in sscanf with "%s %s" as format, sprintf will
cause a read warning on the same format with the same char arrays, e.g.

==4995== Invalid read of size 1
==4995==    at 0x52A9040: vfprintf (vfprintf.c:1655)
==4995==    by 0x52CDAA3: vsprintf (iovsprintf.c:42)
==4995==    by 0x52B01D6: sprintf (sprintf.c:32)
==4995==    by 0x4194A8: xf_do_job (xphireengine.c:1911)
==4995==    by 0x4119C6: xf_main (xphireengine.c:642)
==4995==    by 0x4110FB: main (xphireengine.c:490)
==4995==  Address 0xffeffd800 expected vs actual:
==4995==  Expected: stack array "tmsg" of size 80 in frame 3 back from here
==4995==  Actual:   stack array "t2msg" of size 80 in frame 3 back from here
==4995==  Actual:   is 0 after Expected

(This comment is added in the hope that it can help users find false positives
from sgcheck).

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]