https://bugs.freedesktop.org/show_bug.cgi?id=67128
--- Comment #13 from Terrence Enger <[email protected]> --- Created attachment 84075 --> https://bugs.freedesktop.org/attachment.cgi?id=84075&action=edit backtrace from later segfault, executing on a 64-bit system With master commit ecb842e, pulled around 2013-08-13 22:30 UTC, built with --enable-dbgutil, the results are different, but further actions lead anyway to a segmentation fault. So, picking up from step (9) of comment 10, my revised report is ... ( 9) Click "Sort Ascending". Program resorts the rows so that all cells visible in column B have 1. Note that the header row has been sorted out-of-sight. (10) Type ctrl-Z. Row 1, in particular, is once again the header row with down-arrow buttons. (11) Click the down-arrow button in cell B1. Program present the pop-up. (12) Click "Sort Descending". Segfault. The backtrace again shows function __gnu_debug :: _Safe_iterator_base :: _M_attach_single ( __gnu_debug :: _Safe_sequence_base * , bool ) So, I conclude that (a) this is, in some ill-defined sense, the same crash; and (b) a non-dbgutil build is unlikely to fail the same way. Still, if the non-dbgutil build is not somehow unclean--perhaps relying on undocumented behaviour of the STL, or something--it would suggest a problem in STL. Unless our code really is different with --enable-dbgutil; I saw a commit fixing one of those bugs in the last few days. -- 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
