On Wed, 20 Feb 2002, Allan Rae wrote:
> [...]
> #4  0x080e9a86 in LyXText::setCursor (this=0x23d16c8, bview=0x317ded8, 
>par=0x30a8e24, pos=0,
>     setfont=true, boundary=false) at ../../lyx-devel/src/text2.C:2101
> #5  0x0813fded in InsetText::edit (this=0x30aa614, bv=0x317ded8, front=true)
>     at ../../../lyx-devel/src/insets/insettext.C:706
> #6  0x08125eb0 in InsetCollapsable::edit (this=0x30aa5b8, bv=0x317ded8, xp=36, 
>yp=-2, button=3)
>     at ../../../lyx-devel/src/insets/insetcollapsable.C:255
> #7  0x08054fad in BufferView::Pimpl::workAreaButtonPress (this=0x317df1c, xpos=36, 
>ypos=-2, button=3)
>     at ../../lyx-devel/src/BufferView_pimpl.C:652
>
>
> Other than a 30 second look at the code telling me this crash is due
> to old_cursor being a dud and not due to dEPM() as such.  Possibly an
> uninitialised cursor or at least an un-updated cursor for the LyXText
> of the minipage.  I couldn't find anything obvious in a 5 minute
> search.  Back to paid work now.

I made a little extra time that I shouldn't have.

Try fixing the #warning area of LyXText::setCursorIntern() since I get

InsetText   is 0x831ed84
inset_owner is 0x831c3bc

in the output just before it crashes and these correspond to:

inset_owner == second inset text  (does this make sense?)
InsetText   == I can't find anything to match.

Now I really should get back to work.

BTW, I tried uncommenting the code after the warnings in that function
but it still crashes.

Allan. (ARRae)

Reply via email to