"Ben" == Ben Cazzolato [EMAIL PROTECTED] writes:
Ben After finally realising that the lyxgdb RPM had a different
Ben binary I now have what I think is a useful trace. I've attached
Ben two dump files (it happened to me twice in a couple of minutes)
Ben when it crashed on me when deleting text.
JM,
Did you document contain tables? I hope this does not mean it is a new
different bug. Anyway thanks for the traces.
Yes it did although I wasn't working on them at the time.
Ben
> "Ben" == Ben Cazzolato <[EMAIL PROTECTED]> writes:
Ben> After finally realising that the lyxgdb RPM had a different
Ben> binary I now have what I think is a useful trace. I've attached
Ben> two dump files (it happened to me twice in a couple of minutes)
Ben> when it crashed on me when
JM,
> Did you document contain tables? I hope this does not mean it is a new
> different bug. Anyway thanks for the traces.
Yes it did although I wasn't working on them at the time.
Ben
And yet another trace (it's my last for this bug I promise). Ahhh, please help
me fix this. It's driving me nuts.
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change
And yet another trace (it's my last for this bug I promise). Ahhh, please help
me fix this. It's driving me nuts.
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change
Kayvan et al.
OK. Lyx has been crashing in the same manner ever since 1.1 was released. The
only problem is it isn't reproducable despite it occuring frequently (weekly).
Can I run the lyxgdb RPM version all the time so that when it does crash I
can go through the same procedure with gdb and
Can I run the lyxgdb RPM version all the time so that when it does crash I
can go through the same procedure with gdb and reproduce a useful trace? Are
there any limitations with the lyxgdb version (I noticed that the gdb RPM was
smaller than the standard RPM)? If not then maybe this should
On Tue, Mar 14, 2000 at 09:01:53AM +, Ben Cazzolato wrote:
Kayvan et al.
OK. Lyx has been crashing in the same manner ever since 1.1 was released. The
only problem is it isn't reproducable despite it occuring frequently (weekly).
Can I run the lyxgdb RPM version all the time so that
Kayvan et al.
OK. Lyx has been crashing in the same manner ever since 1.1 was released. The
only problem is it isn't reproducable despite it occuring frequently (weekly).
Can I run the lyxgdb RPM version all the time so that when it does crash I
can go through the same procedure with gdb and
> Can I run the lyxgdb RPM version all the time so that when it does crash I
> can go through the same procedure with gdb and reproduce a useful trace? Are
> there any limitations with the lyxgdb version (I noticed that the gdb RPM was
> smaller than the standard RPM)? If not then maybe this
On Tue, Mar 14, 2000 at 09:01:53AM +, Ben Cazzolato wrote:
> Kayvan et al.
>
> OK. Lyx has been crashing in the same manner ever since 1.1 was released. The
> only problem is it isn't reproducable despite it occuring frequently (weekly).
> Can I run the lyxgdb RPM version all the time so
Allan
Here's the additional stuff as requested. Hope I got it
right. I have absolutely no idea what I'm doing..
gdb /usr/bin/lyx core 21 | tee temp.txt
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the
On Mon, 13 Mar 2000, Ben Cazzolato wrote:
Allan
Here's the additional stuff as requested. Hope I got it
right. I have absolutely no idea what I'm doing..
You did very well except for one small but critical detail.
A binary with debugging information compiled in is needed
On Tue, Mar 14, 2000 at 09:41:39AM +1000, Allan Rae wrote:
You need to either recompile lyx using
./configure --with-debug
or get Kayvan's lyxgdb rpm.
In fact, I just made a lyxgdb RPM for lyx-1.1.4-fix2
It contains a ``lyxgdb'' binary which is lyx-1.1.4-fix2 binary
with all the
Allan
Here's the additional stuff as requested. Hope I got it
right. I have absolutely no idea what I'm doing..
gdb /usr/bin/lyx core 2>&1 | tee temp.txt
GNU gdb 4.17.0.11 with Linux support
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the
On Mon, 13 Mar 2000, Ben Cazzolato wrote:
> Allan
>
> Here's the additional stuff as requested. Hope I got it
> right. I have absolutely no idea what I'm doing..
You did very well except for one small but critical detail.
A binary with debugging information compiled in is
On Tue, Mar 14, 2000 at 09:41:39AM +1000, Allan Rae wrote:
>
> You need to either recompile lyx using
> ./configure --with-debug
>
> or get Kayvan's lyxgdb rpm.
In fact, I just made a lyxgdb RPM for lyx-1.1.4-fix2
It contains a ``lyxgdb'' binary which is lyx-1.1.4-fix2 binary
with all
On Sat, 11 Mar 2000, Ben Cazzolato wrote:
Is the following better
Yes although you should also do a few other things...
(gdb) where
followed by:
up
until you get to...
#0 0x401e0111 in __kill ()
#1 0x401dfd66 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x401e1447
On Sat, 11 Mar 2000, Ben Cazzolato wrote:
> Is the following better
Yes although you should also do a few other things...
>
> (gdb) where
followed by:
up
until you get to...
> #0 0x401e0111 in __kill ()
> #1 0x401dfd66 in raise (sig=6) at ../sysdeps/posix/raise.c:27
> #2
On Sat, Mar 11, 2000 at 02:52:19PM +, Ben Cazzolato wrote:
Guys
Was deleting some text when Lyx crashed. Is the following useful to help track
the bug down?
#0 0x401e0111 in __kill ()
(gdb) q
No, it's not useful. You should have typed "where" to see the call stack.
Ahhh,
Was deleting some text when Lyx crashed. Is the following useful to help
track the bug down?
#0 0x401e0111 in __kill ()
(gdb) q
No, it's not useful. You should have typed "where" to see the call stack.
Is the following better
(gdb) where
#0 0x401e0111 in
On Sat, Mar 11, 2000 at 02:52:19PM +, Ben Cazzolato wrote:
> Guys
>
> Was deleting some text when Lyx crashed. Is the following useful to help track
> the bug down?
>
> #0 0x401e0111 in __kill ()
> (gdb) q
No, it's not useful. You should have typed "where" to see the call stack.
Ahhh,
> > Was deleting some text when Lyx crashed. Is the following useful to help
track > > the bug down?
> >
> > #0 0x401e0111 in __kill ()
> > (gdb) q
>
> No, it's not useful. You should have typed "where" to see the call stack.
Is the following better
(gdb) where
#0
24 matches
Mail list logo
