[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs crash
From: |
Kenichi Handa |
Subject: |
Re: emacs crash |
Date: |
Fri, 30 Nov 2001 17:20:41 +0900 (JST) |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) |
ET <eli@beach.weizmann.ac.il> writes:
> this is an emacs crash that requires my .emacs file etc, but it is
> reproducible, so I can run emacs under gdb to investigate this. I
> have done the most trivial things here using gdb:
> where/backgrace/xbacktrace. I will be glad to do more, but I will
> need PRECISE instructions on what gdb commands to use.
I couldn't reproduce that bug. Please tell us the output of
the following gdb commands?
> #0 0x08083109 in decode_coding_iso2022 (coding=0xbffe58b0,
> source=0xbffe5b50 " other pressing environmental\nproblems requires a
> wealth of information that is difficult to measure\ndirectly. Chief among
> these is data related to ocean currents and the\nexchange of heat between
> the"...,
(gdb) p coding->symbol
(gdb) pr
(gdb) up 2
> #2 0x08151752 in Fcall_process (nargs=6, args=0xbffe9be4) at callproc.c:792
(gdb) p args[0]
(gdb) pr
(gdb) p args[1]
(gdb) pr
(gdb) p args[5]
(gdb) pr
(gdb) p args[6]
(gdb) pr
---
Ken'ichi HANDA
handa@etl.go.jp