Sebastian wrote:
On Fri, Oct 24, 2014, Sebastian Geerken wrote:
I've problems to reproduce it, but I'm guessing ...
On Do, Okt 23, 2014, eocene wrote:
(gdb) bt #0 0xb778a424 in __kernel_vsyscall () #1 0xb70b2661 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0xb70b5a92 in *__GI_abort () at abort.c:92 #3 0xb70ab878 in *__GI___assert_fail ( assertion=0x816049e "i >= 0 && this->num - i > 0", file=0x816048e "../lout/misc.hh", line=167, function=0x8160540 "T* lout::misc::SimpleVector<T>::getRef(int) const [with T = dw::Textblock::Line]") at assert.c:81 #4 0x080a73f6 in lout::misc::SimpleVector<dw::Textblock::Line>::getRef ( this=0x905df50, i=-1) at ../lout/misc.hh:167 #5 0x080a8447 in dw::Textblock::TextblockIterator::getAllocation ( this=0x885ef98, start=0, end=5, allocation=0xbff2e818) at textblock_iterator.cc:288
A line is missing, but everything else seems OK. I guess that this has to do with the new line breaking (introduced with release 3.0.3), where some words are not immediately assigned to a line. I'll soon work on this.
I just pushed a fix. Does the problem still occur?
I'll probably be lucky to trigger the right conditions again, but I'll try to make a habit of searching for text while waiting for pages to load and render...