diff options
| author | Stephan Bergmann <sbergman@redhat.com> | 2014-05-21 18:22:27 +0200 |
|---|---|---|
| committer | Stephan Bergmann <sbergman@redhat.com> | 2014-05-21 18:29:57 +0200 |
| commit | 8f97326bdd3f42fc82aa5e1989fd03b0af1daf64 (patch) | |
| tree | 7c1000a821d3d895a8c3c0abb8620f2e882d5205 /swext | |
| parent | c5a603ce2469ef6a23023ff276ccd24ca316f6c2 (diff) | |
So ZCodec::ReadAsynchron was wrong in using a persistent mpIStm after all
The fun thing is that with the (only) call-site to ReadAsynchron in
PNGReaderImpl::ImplReadIDAT (vcl/source/gdi/pngread.cxx) passing in rIStm
references to stack-allocated SvMemoryStream instances, mpIStm could point to an
old, destroyed instance from a previous call, but which would have been located
at exactly the same stack address as the currently passed in rIStm, so the wrong
mpIStm->Read call would effectively behaved exactly the same as a correct
rIStm.Read call.
This went unnoticed "since the beginning" until AddressSanitizer's
UseAfterReturn check came along...
Change-Id: I7c75ed2d36a4c24c111d88eff647816bd2c5dbca
Diffstat (limited to 'swext')
0 files changed, 0 insertions, 0 deletions