On Wed, Apr 25, 2007 at 11:12:22PM +0200, Abdelrazak Younes wrote: > Martin Vermeer wrote: > >On Wed, Apr 25, 2007 at 10:27:36PM +0200, Abdelrazak Younes wrote: > >>Bennett Helm wrote: > >>>On Apr 25, 2007, at 4:11 PM, Abdelrazak Younes wrote: > >>> > >>>>Bennett Helm wrote: > >>>>>On the User's List, Scott Lambert reported -- and I can confirm -- a > >>>>>problem with opening documents when LyX is not currently running. > >>>>>Simply double-clicking the document icon (or dragging it onto the LyX > >>>>>icon in the Dock) launches LyX.app, which then immediately quits. > >>>>>Console spits out the following: > >>>>>Assertion triggered in lyx::BufferView* lyx::LyXFunc::view() const by > >>>>>failing check "lyx_view_" in file lyxfunc.C:2105 > >>>>I need a backtrace. > >>>I was afraid you'd say that: I'm not sure how to produce one. (Can I use > >>>gdb to open a document which itself starts LyX?) > >>Hum, it's gonna be difficult indeed. > > > >How about getting a core dump, and using that to extract the backtrace? > > Looks like it's feasible! > > Bennett, you just have to replace the executable pointed by the icon > with an executable with full debug info. The crash will hopefully > generate a lyx.core or something (my memory of unix is fading). > > Then running "gdb lyx.core" and "bt" will get you there, I hope.
I remember something like ulimit -c <very-large-number> to allow the core file to be created. - Martin
