diff options
author | Eike Rathke <erack@redhat.com> | 2015-12-11 14:27:33 +0100 |
---|---|---|
committer | Eike Rathke <erack@redhat.com> | 2015-12-11 14:44:41 +0100 |
commit | 9c1ba0988f5db05bb796eaf7cf902a0b601c6736 (patch) | |
tree | 0dca46f5fe5ed8e710115ab0735c748e2373a3d5 /svtools/inc/pch/precompiled_svt.cxx | |
parent | edbe61b671bc4c384be914099ee8bcdfd8491f3a (diff) |
geez, how about actually checking the Move() error return? tdf#92779 related
Handle failure condition where we know how to treat it, i.e. when
updating references, assert in all other places that so far silently
ignored it and implicitly assumed the failing Move() truncating at
bounds would be alright. In case we'll encounter an assertion we'll have
to inspect those places and decide what to do about it.
Noticed this error with a reference like B1048575 and inserting two rows
above, it became B1048576 instead of B#REF!
Change-Id: I00757f3ed2e305b591178047933ed60f1533317e
Diffstat (limited to 'svtools/inc/pch/precompiled_svt.cxx')
0 files changed, 0 insertions, 0 deletions