From: Michael Albinus <michael.albinus@gmx.de>
To: Thierry Volpiatto <thievol@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org, 55832@debbugs.gnu.org
Subject: bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29
Date: Fri, 10 Jun 2022 14:20:15 +0200 [thread overview]
Message-ID: <87k09ohfr4.fsf@gmx.de> (raw)
In-Reply-To: <87edzwakji.fsf@posteo.net> (Thierry Volpiatto's message of "Fri, 10 Jun 2022 10:00:12 +0000")
Thierry Volpiatto <thievol@posteo.net> writes:
> Hello Michael,
Hi Thierry,
>> First, I've tried to reproduce it from emacs -Q. I've upgraded all
>> installed ELPA packages, and then I have called
>>
>> emacs -Q \
>> -l ~/.emacs.d/elpa/helm-core-20220503.622/helm-core-autoloads.el \
>> -l ~/.emacs.d/elpa/helm-20220504.827/helm-autoloads.el \
>> -l ~/.emacs.d/elpa/helm-tramp-20190616.125/helm-tramp-autoloads.el \
>
> What is helm-tramp? this is not part of helm.
I've installed this as ELPA package a while ago, don't remember the
details. So I've taken this out, calling now Emacs master branch like
emacs -Q \
-l ~/.emacs.d/elpa/helm-core-20220503.622/helm-core-autoloads.el \
-l ~/.emacs.d/elpa/helm-20220504.827/helm-autoloads.el \
-l ~/.emacs.d/elpa/async-20220318.1342/async-autoloads.el -l seq
> You have better time cloning emacs-async and run make && sudo make
> install and same with helm, then emacs -q, (require 'helm) (require
> 'helm-config) and C-x c C-x C-f
Hmm, this would poison my laptop with an undesired config. Shouldn't the
call above be sufficient?
>> Using /sudo:: as file name doesn't raise any error.
>
> Did you follow the recipe I sent?
> First shot doesn't crash but second after M-x
> tramp-cleanup-all-connections does.
Ahh, this was another message I didn't notice.
>> However, this is from the master branch;
>
> The bug is from master branch not emacs-28, I sent the bug report from
> my main emacs which is emacs-28 because 29 crashed.
OK, rerunning your recipe with the invocation as above:
> 1) Ensure you have no entries for sudo in .authinfo.gpg file.
Not needed, because I call "emacs -Q".
> 2) M-x helm-find-files RET // sudo::
Done.
> 3) You are prompted for password
Yep.
> 4) At this first shot it should work as expected.
Not clear to me whether I shall enter the password. I did. Now Helm
offers me something, which I always confirm with RET, until I see the
dired buffer of "/sudo:root@gandalf:/root". "gandalf" is the name of my laptop.
> 5) C-g to quit, and M-x tramp-cleanup-all-connections.
Done.
> 6) Restart helm-find-files and enter /sudo:: emacs should freeze and crash.
I've switched to the *scratch* buffer, and did this. No problem.
-----
Now a second attempt. Steps 1-3 as above.
> 4) At this first shot it should work as expected.
I didn't enter the password.
> 5) C-g to quit, and M-x tramp-cleanup-all-connections.
Done. I have applied C-g twice in order to go out of the minibuffer.
> 6) Restart helm-find-files and enter /sudo:: emacs should freeze and crash.
No, Emacs asks me for the /sudo:: password, and continues as expected.
>> tramp-get-remote-uid *is* a valid argument, and
>> tramp-file-name-for-operation shouldn't raise an error. Once we have
>> fixed the problem of Emacs crash, it shall be investigated wy this error
>> has been raised.
>
> tramp-get-remote-uid is calling tramp-file-name-handler with
> tramp-get-remote-uid as arg so I guess the infinite recursion starts
> here isn't it?
No. tramp-get-remote-uid invokes tramp-file-name-handler in order to get
a method specific implementation (finally, tramp-sh-handle-get-remote-uid
shall be called).
>> It is not clear to me why tramp-file-name-for-operation goes into
>> recursion with the error handling, invoking again and again
>> tramp-signal-hook-function (that is the function bound to
>> signal-hook-function).
>
> What is calling tramp-get-remote-uid in tramp-file-name-for-operation?
tramp-get-remote-uid should *not* be called inside
tramp-file-name-for-operation. The symbol is passed as argument, and
used for investigation of the other args.
>> Similar protections have been applied already elsewhere in Tramp. Does
>> this solve the problem?
>
> No still crashing.
Sad. Since I cannot reproduce the problem locally, what happens if you
invoke "emacs -Q" similar to how I've done?
Best regards, Michael.
next prev parent reply other threads:[~2022-06-10 12:20 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 15:16 bug#55832: 28.1; Emacs crashes when using tramp from helm in emacs-29 Thierry Volpiatto
2022-06-07 16:08 ` Eli Zaretskii
2022-06-07 17:02 ` Thierry Volpiatto
2022-06-07 17:18 ` Eli Zaretskii
2022-06-07 18:33 ` Thierry Volpiatto
2022-06-07 18:53 ` Eli Zaretskii
2022-06-07 19:20 ` Thierry Volpiatto
2022-06-08 13:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-08 16:30 ` Eli Zaretskii
2022-06-08 18:17 ` Lars Ingebrigtsen
2022-06-08 18:25 ` Eli Zaretskii
2022-06-09 10:34 ` Lars Ingebrigtsen
2022-06-09 10:42 ` Thierry Volpiatto
2022-06-09 13:05 ` Eli Zaretskii
2022-06-09 15:18 ` Thierry Volpiatto
2022-06-09 15:29 ` Lars Ingebrigtsen
2022-06-09 16:36 ` Eli Zaretskii
2022-06-09 16:51 ` Thierry Volpiatto
2022-06-09 17:48 ` Eli Zaretskii
2022-06-09 18:28 ` Thierry Volpiatto
2022-06-09 18:55 ` Eli Zaretskii
2022-06-10 7:53 ` Michael Albinus
2022-06-10 10:00 ` Thierry Volpiatto
2022-06-10 12:20 ` Michael Albinus [this message]
2022-06-11 6:14 ` Thierry Volpiatto
2022-06-11 19:27 ` Michael Albinus
2022-06-11 19:46 ` Thierry Volpiatto
2022-06-11 20:07 ` Michael Albinus
2022-06-11 20:12 ` Thierry Volpiatto
2022-06-12 18:16 ` Thierry Volpiatto
2022-06-14 11:39 ` Michael Albinus
2022-06-14 11:49 ` Thierry Volpiatto
2022-06-09 15:37 ` Thierry Volpiatto
2022-06-14 11:05 ` Michael Albinus
2022-06-14 11:36 ` Thierry Volpiatto
2022-06-14 11:44 ` Michael Albinus
2022-06-14 17:42 ` Michael Albinus
2022-06-16 17:27 ` Michael Albinus
2022-06-16 18:11 ` Thierry Volpiatto
2022-06-17 16:54 ` Michael Albinus
2022-06-17 17:10 ` Thierry Volpiatto
2022-06-19 14:25 ` Michael Albinus
2022-06-19 16:21 ` Thierry Volpiatto
2022-06-19 17:51 ` Michael Albinus
2022-06-21 8:24 ` Michael Albinus
2022-06-21 9:35 ` Thierry Volpiatto
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=87k09ohfr4.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=55832@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=thievol@posteo.net \
/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).