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.
>