Date: Wed, 12 Dec 2001 10:38:42 -0500 From: dochawk@psu.edu To: John Levon <moz@compsoc.man.ac.uk>, lyx-devel@lists.lyx.org Cc: dochawk@psu.edu, freebsd-questions@FreeBSD.ORG Subject: Re: crash deleting in table Message-ID: <200112121538.fBCFcg848448@fac13.ds.psu.edu> In-Reply-To: Your message of "Wed, 12 Dec 2001 15:24:54 GMT." <20011212152454.A83503@compsoc.man.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
john joined, > On Wed, Dec 12, 2001 at 10:20:52AM -0500, dochawk@psu.edu wrote: > > > On Tue, Dec 11, 2001 at 03:22:56PM -0500, Richard E. Hawkins wrote: > > > > Program received signal SIGSEGV, Segmentation fault. > > > > LyXText::init (this=0x8326000, bview=0x836fd00, reinit=false) at text2.C:95 > > > > 95 setCursorIntern(bview, firstrow->par(), 0); > > > > (gdb) bt > > > > #0 LyXText::init (this=0x8326000, bview=0x836fd00, reinit=false) at text2.C:95 > > > so firstrow is null or wrong. can you print out the value in gdb ? > > how do I do htat? > do "up" until you get to the right piece of code then : > print firstrow so I'l recognized the "right piece" when I see something like the setCursorIntern offered to me? (no hablo gdb :) > > later operation in the same table that is causing the crash (with > > operator meaning more than simply typing data-cut, paste, delete, table > > operations, etc.) > yes, they look cursor placement and re-init problems. it is unfortunate > they are unreproducable as this often makes it really hard for us to > see what bug is there ... would cores be useful? hawk -- What part of "non-negotiable" didn't you understand? /"\ ASCII ribbon campaign dochawk@psu.edu Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of X and postings. Penn State until it pays my retainer. / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200112121538.fBCFcg848448>