unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Iain Buchanan <iain@pcorp.com.au>
Subject: Re: possible bug in emacs
Date: 14 Aug 2002 09:10:17 +0930	[thread overview]
Message-ID: <1029282017.5842.12.camel@orpheus> (raw)
In-Reply-To: <2110-Tue13Aug2002125243+0300-eliz@is.elta.co.il>

[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]

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


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2002-08-13 23:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12 23:34 possible bug in emacs Iain Buchanan
2002-08-13  9:52 ` Eli Zaretskii
2002-08-13 23:40   ` Iain Buchanan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1029282017.5842.12.camel@orpheus \
    --to=iain@pcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).