From: Ben Beecher <benbeecher@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 7402@debbugs.gnu.org
Subject: bug#7402: 23.2; loading tramp causes emacs to freeze
Date: Mon, 15 Nov 2010 11:08:30 -0500 [thread overview]
Message-ID: <AANLkTikfVhCfZdDm-wB2icrnO6mU_8FbD4jzV+Mo1p8s@mail.gmail.com> (raw)
In-Reply-To: <87y68u52ip.fsf@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
Hey Michael - Thanks for taking a look at this.
Attempting to load a networked file also crashes emacs.
Unfortunately setting debug-on-signal or debug-on-quit doesn't produce a
backtrace - emacs won't respond to C-g and I have to kill the emacs process.
Tonight 'll attempt to run the emacs process under gdb, and grab a stack
trace that way.
On Mon, Nov 15, 2010 at 5:01 AM, Michael Albinus <michael.albinus@gmx.de>wrote:
> Ben Beecher <benbeecher@gmail.com> writes:
>
> > Emacs Crashes as soon as I load Tramp - to replicate:
> >
> > emacs -Q
> > M-: (require 'tramp)
> >
> > After requiring tramp emacs freezes. Running top shows that emacs is
> > grabbing ram as fast as it can untill I kill it.
>
> What happens, if you don't require Tramp, but open a remote file (or
> directory) instead of? Something like
>
> emacs -Q
> C-x C-f /ssh::
>
> Furthermore, could you, please, apply (setq debug-on-signal t) before
> running the test. Immediately after Tramp hangs, try to kill it with
> C-g and show the backtrace.
>
> Best regards, Michael.
>
[-- Attachment #2: Type: text/html, Size: 1498 bytes --]
next prev parent reply other threads:[~2010-11-15 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-14 22:39 bug#7402: 23.2; loading tramp causes emacs to freeze Ben Beecher
2010-11-15 10:01 ` Michael Albinus
2010-11-15 16:08 ` Ben Beecher [this message]
2010-11-15 16:21 ` Michael Albinus
2011-01-18 19:38 ` Hans Rosenfeld
2011-01-19 9:12 ` Michael Albinus
2011-01-19 10:20 ` Hans Rosenfeld
2011-01-19 16:47 ` Michael Albinus
2011-01-19 18:32 ` Hans Rosenfeld
2011-01-19 21:41 ` Michael Albinus
2013-03-09 13:29 ` Michael Albinus
2013-03-27 20:56 ` Hans Rosenfeld
2013-03-27 21:50 ` Michael Albinus
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=AANLkTikfVhCfZdDm-wB2icrnO6mU_8FbD4jzV+Mo1p8s@mail.gmail.com \
--to=benbeecher@gmail.com \
--cc=7402@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).