Re: tramp_file_attributes

[Kai Großjohann]

Sven Gabriel <address@hidden> writes:

> It works fine to an alpha workstation, connecting to a fujitsu-siemens vector 
> maschine results in a Memory fault after  tramp_file_attributes...
> the funny thing is, that I get the listing of the home Directory:
> -----------------------------------------------------------------------------------------------
> $ tramp_file_attributes /home/
> (t 9 0 0 (16146 41687) (15550 54354) (15550 54354) 512 16877 t (0 . 2) (500 
> 2054))
> -----------------------------------------------------------------------------------------------
> changing to /home/vpp5000 results in:
> -----------------------------------------------------------------------------------------------
> $ ( test -d /home/vpp5000 2>/dev/null; echo tramp_exit_status $? )
> tramp_exit_status 0
> $ ( test -d /home/vpp5000 2>/dev/null; echo tramp_exit_status $? )
> tramp_exit_status 0
> $ ( test -d /home/vpp5000 2>/dev/null; echo tramp_exit_status $? )
> tramp_exit_status 0
> $ ls -d /home/vpp5000/.dired 2>/dev/null; echo tramp_exit_status $? 
> tramp_exit_status 2
> # Inserting directory `ls -al /[scp/vpp]/home/vpp5000/', wildcard no, fulldir 
> yes
[...]
> $ cd
> $ ls -d /home/vpp5000/ 2>/dev/null; echo tramp_exit_status $? 
> /home/vpp5000/
> tramp_exit_status 0
> $ tramp_file_attributes /home/vpp5000/
> Memory fault
> ------------------------------------------------------------------------------------------

That's a most fascinating phenomenon.  In the debug buffer you can
see what Tramp is sending to the remote end.  In particular, the
tramp_file_attributes shell function is of interest here.

Could you log in to the machine normally (outside of Emacs), then
invoke a Bourne-ish shell ("exec /bin/sh"), then send the
tramp_file_attributes implementation (copy and paste from the debug
buffer should do), then invoke it there on various files and
directories to see what happens?  Do you also get a memory fault from
Perl when you do that?
-- 
~/.signature