#1484 [patch] fix incorrect memory access
Metadata
Property | Value |
---|---|
Reported by | Andreas Lauser (andreas.lauser@iws.uni-stuttgart.de) |
Reported at | Aug 17, 2014 15:42 |
Type | Bug Report |
Version | 2.3 |
Operating System | Unspecified / All |
Last edited by | Oliver Sander (oliver.sander@tu-dresden.de) |
Last edited at | Aug 18, 2014 09:39 |
Closed by | Oliver Sander (oliver.sander@tu-dresden.de) |
Closed at | Aug 18, 2014 09:39 |
Closed in version | Unknown |
Resolution | Fixed |
Comment | in fe8cb3dca8890a4ab67462f4f43c841db05e90dc |
Thanks! |
Description
commit message: parameter tree parser: do not try to access the first character of empty strings
funnily enough, this usually worked (i.e. it returned some garbage
which was not recognized by the switch statement that followed), and
was not detected by valgrind (on my machine at least, I suppose this
was because the address to which the string pointed was still a valid
memory location created by some previous user). The libstdc++ debug
mode (-D_GLIBCXX_DEBUG=1 -D_GLIBCXX_DEBUG_PEDANTIC=1) did find it
though...