On Sat, Jan 05, 2002 at 12:04:07PM +0100, Michael Schmitt wrote: > - Operation not known exactly:
I bet this is the same as your other bug where the delete empty para mechanism comes in and removes a paragraph from under BufferView::removeAutoInsets() (after all it's a crash, what else could it be but that mechanism ;) I guess Lars knows how to fix it (he changed this last). > FMR: Free memory read: > * This is occurring while in: > BufferView::removeAutoInsets() [BufferView2.C:128] > LyXFunc::dispatch(int,const lyxstring&) [lyxfunc.C:1142] > Menubar::Pimpl::MenuCallback(flobjs_*,long) [Menubar_pimpl.C:586] > C_Menubar_Pimpl_MenuCallback [Menubar_pimpl.C:79] > - Operation not known exactly but this error seems to be THE REASON FOR MANY, MANY >PROBLEMS :-) > > UMR: Uninitialized memory read: > * This is occurring while in: > InsetTabular::insetInInsetY() [insettabular.C:703] > BufferView::fitLockedInsetCursor(int,int,int,int) [BufferView2.C:499] hmm, this looks like the_locking_inset is referring to a deleted inset. I don't get this code too much ... > - Open preferences dialog: > > UMR: Uninitialized memory read: > * This is occurring while in: > FileInfo::isDir()const [FileInfo.C:343] > RWInfo::WriteableFile(const lyxstring&) [xforms_helpers.C:477] FileInfo is sucky. Clients needs to check that .isOK() before they query anything else. I'll do an audit of all FileInfo users and fix the bad ones unless someone has a suggestion for improving FileInfo somehow in the lack of exceptions ... > - Include a (faulty?) TeX file into an empty document; press return in front > of the include inset such that the cursor is now in an empty paragraph; export > to DVI -> crash this is the bug I refer to at the top. regards john
