https://bugs.freedesktop.org/show_bug.cgi?id=73294
--- Comment #16 from Jim Avera <jim.av...@gmail.com> --- Running with valgrind discloses a couple of problems, both of which I think indicate real bugs: 1. Valgrind reports some 8-byte reads which extend 4 bytes beyond the end of malloc'd space. This would cause unpredictable garbage to be returend in the last 4 bytes, and might possibly explain some Basic macro bugs I've been chasing which vanish when print statements are put in. The 8 vs. 4 byte lengths might indicate a bug in some low-level casts related to platform word-size. This was previously reported but rejected as "NOTABUG" because the offending code is somewhere in Phython bindings. I don't see how it can not be a bug. Please see https://bugs.freedesktop.org/show_bug.cgi?id=78513 2. Today I re-ran the test for the present bug under Valgring using the option --free-fill=DE, which causes all free'd heap block to be filled with 0xDE values. Doing this made the demo behave very differently -- I got several Basic errors I never saw before. The implication is that LO is referencing memory *after* it has been freed onto the heap. In summary, I strongly recommend running under valgrind and tracking down and removing all references to undefined (i.e., not currently allocated) memory. -- 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
