[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: possible bug in emacs
From: |
Iain Buchanan |
Subject: |
Re: possible bug in emacs |
Date: |
14 Aug 2002 09:10:17 +0930 |
On Tue, 2002-08-13 at 19:22, Eli Zaretskii wrote:
> > From: Iain Buchanan <iain@pcorp.com.au>
> > Date: 13 Aug 2002 09:04:39 +0930
> >
> > various actions cause emacs to seg fault. Usually mouse clicking somewhere
> > within the file. I am not a gdb master but I attached gdb to a running
> > emacs process (that always died on a particular file when I clicked
> > anywhere)
> > and this is what it said...
>
> Please see the file etc/DEBUG in the distribution for some guidelines
> about debugging Emacs.
>
> > <<< --- click in emacs here --- >>>
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x080505e4 in increment_row_positions ()
> > (gdb) continue
> > Continuing.
>
> At this point, instead of "continue", type "bt". This should print
> the C-level backtrace of function calls that led to the crash.
> Please post that backtrace here.
>
> Thanks.
Oops sorry, I thought I included all the version info. It must have
been late...
GNU Emacs 21.2.1
RedHat 7.3
Linux 2.4.18-5
Program received signal SIGSEGV, Segmentation fault.
0x080505e4 in increment_row_positions ()
(gdb) bt
#0 0x080505e4 in increment_row_positions ()
#1 0x0804fe2b in increment_matrix_positions ()
#2 0x08067b6b in redisplay_internal ()
#3 0x080575f8 in sit_for ()
#4 0x080d97c3 in command_loop_1 ()
#5 0x0812e13c in internal_condition_case ()
#6 0x080d8a18 in command_loop_2 ()
#7 0x0812dcb6 in internal_catch ()
#8 0x080d8994 in command_loop ()
#9 0x080d84dd in recursive_edit_1 ()
#10 0x080d860f in Frecursive_edit ()
#11 0x080d74bb in main ()
#12 0x402ff1c4 in __libc_start_main () from /lib/libc.so.6
Iain
signature.asc
Description: This is a digitally signed message part