Lars Gullik Bjønnes wrote:
> Alfredo Braunstein <[EMAIL PROTECTED]> writes:
>
> | With current cvs, only by opening and closing some documents randomly,
> | at some point I get this abort.
> |
> | I doesn't happend very often (and doesn't depend on the particular
> | documents).
>
> Is this a non-optimized build (-O0)?
>
> If not, can you repeat with such a build?
> (It won't necessarily make a difference)
It wasn't, but it doesn't make a difference. I got the same bt. Then
retrying under gdb, I got also this one:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1089852768 (LWP 30102)]
0x0812c1a2 in Paragraph::getPositionOfInset(Inset const*) const (
this=0x8668348, inset=0x8606c08) at /home/ab/lyx-cvs/src/paragraph.C:742
742 if (it->inset == inset)
(gdb) bt
#0 0x0812c1a2 in Paragraph::getPositionOfInset(Inset const*) const (
this=0x8668348, inset=0x8606c08) at /home/ab/lyx-cvs/src/paragraph.C:742
#1 0x0814d821 in LyXText::workWidth(Inset const*) const (this=0x8662aa8,
inset=0x8606c08) at /home/ab/lyx-cvs/src/text.C:155
#2 0x08204afa in UpdatableInset::getMaxWidth(BufferView*, UpdatableInset
const*) const (this=0x8606c08, bv=0x851c578)
at /home/ab/lyx-cvs/src/insets/updatableinset.C:145
#3 0x08204ae2 in UpdatableInset::getMaxWidth(BufferView*, UpdatableInset
const*) const (this=0x8606c5c, bv=0x851c578)
at /home/ab/lyx-cvs/src/insets/updatableinset.C:143
#4 0x081fe7fb in InsetText::getMaxWidth(BufferView*, UpdatableInset const*)
const (this=0x8606c5c, bv=0x851c578, inset=0x8606c5c)
at /home/ab/lyx-cvs/src/insets/insettext.C:1932
#5 0x081f8845 in InsetText::textWidth(BufferView*, bool) const (
this=0x8606c5c, bv=0x851c578, fordraw=false)
at /home/ab/lyx-cvs/src/insets/insettext.C:304
#6 0x0814d77a in LyXText::workWidth() const (this=0x8736620)
at /home/ab/lyx-cvs/src/text.C:142
#7 0x081502a9 in LyXText::rowBreakPoint(Row const&) const (this=0x8736620,
[EMAIL PROTECTED]) at /home/ab/lyx-cvs/src/text.C:778
#8 0x0815301b in LyXText::breakAgain(std::_List_iterator<Row, Row&, Row*>)
(
this=0x8736620, rit=
{<_List_iterator_base> = {_M_node = 0x87947c0}, <No data fields>})
Probably due to heap corruption I'd say. Umph, I'll have to install
valgrind.
> What signal handler and why. What is raising a signal here?
No idea. Suggestions to find it out welcomed.
Alfredo
