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: Sun, 27 Apr 2003 15:49:29 +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?). 

I don't remember whether I've contacted you before.  (I think I did,
but I can't find the message.)  So to be on the safe side, I'll do it
now (again?).

It is difficult to track down bugs that don't happen again.  I'm
afraid the first thing you need is a method to reproduce the
problem.

Then you should run Emacs under the debugger.  Change to the CVS
working directory for Emacs, and then into its subdir src.  There you
will find a .gdbinit file which is needed for the debugging.

Now start Emacs under gdb: "gdb emacs".
Now start Emacs with the usual command line args: "run ...args.go.here..."

Now you just use Emacs until it crashes.

After the crash, you can use the gdb builtin "backtrace" and the
command "xbacktrace" which is defined in .gdbinit to investigate.

Also see the file etc/DEBUG which comes with Emacs, and perhaps the
.gdbinit file itself to learn which other debugger commands are
available.

Hope this helps.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)




reply via email to

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