On Thu, 25 Feb 1999, Bruce M Beach wrote:
> Hello All
>
> I was filling in a table and I thought "What a great idea if .."
> No I'm kidding you.
>
> Start again
> I was filling in a table(entering 0,'s and 1's as text)
> when the pgm dumped core. Of interest is that the emergency
> save file was truncated to the unusual size of 8192.( The
This seems strange... Hmmm... I suspect that the last line or two might
be just before or in the middle of your table that went bang.
> original size was 69635 ) I have the dumped core. I read somewhere
> that you could apply gdb to core to get a bug report. Does anyone
> know how to do that.
>
> Bruce
The following assumes you weren't using a stripped binary.
(If you were you might still get something useful out of it but its going
to be very limited)
gdb /path-to-lyx/lyx core
The path should only be needed if you have multiple lyxs installed.
Once in gdb:
bt
this will give a backtrace of all the functions called made up to the
crash. You'll probably see that the fuction the actual crash occurred in
is marked as ?????. So:
up
this take you up the stack -- keep going until you are one level above the
???? this should display a source line with the actual call to the
function ?????.
It can also be very helpful to use
info locals
as you go up the stack as this provides us with extra info about the
states of the variables. In fact, this is often how the most significant
info in determining the cause of a crash.
Allan. (ARRae)
