https://bugs.documentfoundation.org/show_bug.cgi?id=78513
Michael Stahl <mst...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mst...@redhat.com
Component|Calc |sdk
Resolution|NOTABUG |NOTOURBUG
Summary|Other: Buffer overrun in |valgrind warnings in
|Python UNO initialization |bundled CPython memory
|(possibly explaining random |allocator
|errors) |
--- Comment #5 from Michael Stahl <mst...@redhat.com> ---
by the way you can just run "soffice --valgrind" to run LO
in valgrind, no custom scripting required.
most of the errors are in CPython's memory allocation stuff, which we
neither wrote nor maintain; if you think there are problems there
please get in contact with the CPython community.
==21827== Invalid read of size 8
==21827== at 0x546D511: __wcscpy_ssse3 (wcscpy-ssse3.S:146)
==21827== Invalid read of size 8
==21827== at 0x53AC1EA: wcschr (wcschr.S:112)
these are extremely likely to be a false positive - the libc
string functions are hyper-optimized and will load
data in 8 byte (or even bigger) chunks into registers
but then only access them until they encounter a 0 byte.
The workaround is to run with --partial-loads-ok=yes
--partial-loads-ok=<yes|no> [default: no]
Controls how Memcheck handles 32-, 64-, 128- and 256-bit naturally
aligned loads from addresses for which some bytes are addressable
and others are not. When yes, such loads do not produce an address
error. Instead, loaded bytes originating from illegal addresses are
marked as uninitialised, and those corresponding to legal addresses
are handled in the normal way.
When no, loads from partially invalid addresses are treated the
same as loads from completely invalid addresses: an illegal-address
error is issued, and the resulting bytes are marked as initialised.
Note that code that behaves in this way is in violation of the ISO
C/C++ standards, and should be considered broken. If at all
possible, such code should be fixed. This option should be used
only as a last resort.
perhaps in the meantime your valgrind won't complain any more
because suppressions were added somewhere.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
