Jürgen Spitzmüller wrote: > Peter Kümmel wrote: >> Seems one of the pointers is not valid. If this is the case >> the bug is at a other place. > > Seems so. Launching LyX with -dbg gui gives some interesting results. For the > non-crashing case (--disable-stdlib-debug): > > Toc: at depth 1, added item 1 Einleitung > Toc: at depth 1, added item 2 Die ersten Schritte mit LyX > Toc: at depth 1, added item 3 Das Schreiben von Dokumenten > Toc: at depth 1, added item 4 Mathematische Ausdrücke > Toc: at depth 1, added item 5 Vermischtes > Toc: at depth 1, added item A Literaturverzeichnis > QToc: type_ 0 toc_models_.size() 1 > QToc: type_ 0 toc_models_.size() 1 > QToc: type_ 0 toc_models_.size() 1 > QToc: type_ 0 toc_models_.size() 1 > QToc: type_ 0 toc_models_.size() 1 > QToc: type_ 0 toc_models_.size() 1 > form_->tocModel()->rowCount 6 > form_->tocModel()->columnCount 1 > > And for the crashing case (stdlib-debug enabled): > > QToc: type_ 894323136 toc_models_.size() 0 > > lyx: SIGSEGV signal caught > Sorry, you have found a bug in LyX. Please read the bug-reporting > instructions > in Help->Introduction and send us a bug report, if necessary. Thanks ! > > I think I don't have to stress that the value of type_ is bizarre. I have no > idea where this obscure value is set. > > Jürgen >
I've added more lyxerr output and use a deep copy of a string instead of a reference at the place were I think it is a problem for stdlib-debug. Could you try it again please? Peter
