https://bugs.freedesktop.org/show_bug.cgi?id=57197
--- Comment #10 from Terrence Enger <[email protected]> --- Created attachment 90574 --> https://bugs.freedesktop.org/attachment.cgi?id=90574&action=edit starting point close to the segfault Here is an easier way to show the segfault. I am calling it the same segfault because of the similarity of the top five frames in the backtraces. (1) Download and open the attached file undo_segfault.odt. The caret is at the end of the text in row 2 column 2 of the table. (2) Type "<tab>". The program adds row 3 to the table. (3) Type "<ctrl>+Z". SEGFAULT. This happens on master commit b092637, fetched 2012-12-06 17:20 UTC, configured: --enable-option-checking=fatal --enable-dbgutil --enable-crashdump --without-system-postgresql --without-myspell-dicts --with-extra-buildid --without-doxygen --with-external-tar=/home/terry/lo_hacking/git/src built and and running debian-wheezy. For comparison, LibreOffice supplied with debian-wheezy, version 3.5.2.4 (Build ID: 350m1` (Build:2)), places the cursor at the start of row 1 cell 1 when it opens the file. I have to move the cursor first. Then "<tab><ctrl>+Z" correctly adds row 3 to the table and removes it again. So, I am setting keyword "regression". The crash is not evident in bibisect versions 40 oldest 40+ latest I take this to indicate that the crash is peculiar to debug builds, and I conclude that the failed attempts to replicate the problem on Win and OSX do not indicate very much. (Of course, the all-nines value of `this` in frame zero of the backtrace is peculiar to a debug build.) So, I am setting Whiteboard "NotBibisectable". -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
