emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tramp] Emacs crashed


From: Kai Großjohann
Subject: Re: [Tramp] Emacs crashed
Date: Thu, 24 Apr 2003 10:14:31 +0200
User-agent: Gnus/5.090019 (Oort Gnus v0.19) Emacs/21.3.50 (gnu/linux)

"Martin Lüthi" <address@hidden> writes:

> Emacs crashed when using Tramp. I was using dired on a IBM AIX file
> system. On Enter (looking at a file) Emacs was gone. Before I was
> browsing through the filesystem, looking at several files.
>
> I cannot reproduce that bug, but I once noticed similar behavior when
> browsing a Sun file system (also not reproducible). Probably a memory
> leak / buffer overflow problem?
>
> Please advice how I can further investigate this bug (core dump?). 

Hello Martin,

I've never seen such crashes.  Hm.  Of course, having a
nonreproducible problem makes it more difficult to diagnose.

Can you run Emacs under the debugger?  That would help a lot, I think.

The procedure goes like this:

    cd ~/work/gnu/emacs/src
    gdb emacs
    run emacs ...your.args.here...

Instead of ~/work/gnu/emacs you should use your own CVS working
directory, of course.  The reason for changing to that directory
first is that it contains a .gdbinit file which helps with debugging
Emacs.

Now, when Emacs crashes, you ought to be able to get a C-level
backtrace using the normal gdb commands.  And you should be able to
get a Lisp-level backtrace, too, using the xbacktrace command
provided in .gdbinit.

You might also wish to look at the file ~/work/gnu/emacs/etc/DEBUG
which contains more information on debugging Emacs.

Does this help at all?
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]