From: Christian Johansson <christian@cvj.se>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 33135@debbugs.gnu.org, Alan Third <alan@idiocy.org>
Subject: bug#33135: 27.0.50; (make-thread) TRAMP interactive freeze macOS 10.14
Date: Tue, 6 Nov 2018 18:50:30 +0100 [thread overview]
Message-ID: <112C9286-C8BE-4869-ACFC-07905FFD6A44@cvj.se> (raw)
In-Reply-To: <22698038-514D-48FF-89AA-EDB24984BEB0@cvj.se>
[-- Attachment #1: Type: text/plain, Size: 3332 bytes --]
I was wrong, interactive threaded tramp over ange-ftp on macos doesn’t work. I have got more crashes lately after I updated branch, not sure if errors help but here are some:
;; Opening remote file
emacs(16737,0x700004306000) malloc: *** error for object 0x11cb50885: pointer being freed was not allocated emacs(16737,0x111d105c0) malloc: *** error for object 0x7ffeefbfb610: pointer being freed was not allocated emacs(16737,0x700004306000) malloc: *** set a breakpoint in malloc_error_break to debug emacs(16737,0x111d105c0) malloc: *** set a breakpoint in malloc_error_break to debug Fatal error 6: Abort trapAbort trap: 6 logout Saving session... ...saving history...truncating history files... ...completed.
;; Renaming file over SSH via tramp
objc[40791]: Invalid or prematurely-freed autorelease pool 0x10200b1c0. Fatal error 6: Abort trapAbort trap: 6
;; another local sudo
emacs(41111,0x70000c892000) malloc: *** error for object 0x70000d093530: pointer being freed was not allocated emacs(41111,0x70000c892000) malloc: *** set a breakpoint in malloc_error_break to debug Fatal error 4: Illegal instructionAbort trap: 6
;; another remote dired over SSH
emacs(40323,0x1181f95c0) malloc: *** error for object 0x103337305: pointer being freed was not allocated emacs(40323,0x1181f95c0) malloc: *** set a breakpoint in malloc_error_break to debug
> 5 nov. 2018 kl. 16:39 skrev Christian Johansson <christian@cvj.se>:
>
> Alright, I’ll see if I can get the error again. I only got it like 2 times in 8 hours so it’s not frequent.
>
> I tried user-interaction via threaded ange-ftp tramp on macOS and it seems to work on your branch. I will try it a bit more this week.
>
> Regards
> Christian
>
>> 5 nov. 2018 kl. 14:49 skrev Michael Albinus <michael.albinus@gmx.de>:
>>
>> Christian Johansson <christian@cvj.se> writes:
>>
>>> Hi Michael
>>
>> Hi Christian,
>>
>>> I haven't experienced a single crash since I started using your
>>> threaded tramp branch but I sometimes get errors like this, but it
>>> doesn't make Emacs crash, I can just retry same operation and it will
>>> work. It seems like sometimes a thread is busy and Emacs tries to
>>> access it in some way and this error occurs, I have replaced sensitive
>>> information with --- below
>>>
>>> Debugger entered--Lisp error: (error "Attempt to accept output from
>>> process *ftp ---...")
>>> accept-process-output(#<process *ftp ---@---*>)
>>> ange-ftp-wait-not-busy(#<process *ftp ---@---*>)
>>> ange-ftp-raw-send-cmd(#<process *ftp ---@---*> "type ascii" nil
>>> (#f(compiled-function (result line host user cmd msg cont nowait)
>>> #<bytecode 0x4ffee879>) "---" "---" "type ascii" nil nil nil) nil)
>>
>> Looks like the ange-ftp process is not assigned to the proper thread. As
>> said, ange-ftp is a special case, it wasn't handled yet.
>>
>> I've pushed a fix to the feature/tramp-thread-safe branch; should work
>> now. Could you pls retest?
>>
>>> I haven't tried threaded tramp that requires user-interaction yet
>>> though since I got ~/.authinfo.gpg working with ange-ftp, I'll see if
>>> I can test that this week
>>
>> Likely, this won't work. Nobody has provided a fix for this problem, yet.
>>
>>> Regards
>>> Christian
>>
>> Best regards, Michael.
[-- Attachment #2: Type: text/html, Size: 9683 bytes --]
next prev parent reply other threads:[~2018-11-06 17:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 10:15 bug#33135: 27.0.50; (make-thread) TRAMP interactive freeze macOS 10.14 Christian Johansson
2018-10-24 10:53 ` Alan Third
2018-10-24 11:12 ` Michael Albinus
2018-10-25 5:08 ` Christian Johansson
2018-10-25 8:35 ` Michael Albinus
2018-11-05 6:03 ` Christian Johansson
2018-11-05 13:49 ` Michael Albinus
2018-11-05 15:39 ` Christian Johansson
2018-11-06 17:50 ` Christian Johansson [this message]
2018-11-07 7:48 ` Michael Albinus
2018-11-08 15:42 ` Christian Johansson
2018-11-09 10:12 ` Michael Albinus
2018-11-09 12:08 ` Christian Johansson
2018-11-11 8:53 ` Michael Albinus
2018-11-11 16:00 ` Christian Johansson
2018-11-14 7:59 ` Christian Johansson
2018-11-14 8:03 ` Christian Johansson
2018-11-14 8:08 ` Michael Albinus
2018-11-16 11:16 ` Christian Johansson
2018-11-16 11:53 ` Michael Albinus
2018-11-16 13:13 ` Christian Johansson
2018-11-16 13:45 ` Michael Albinus
2018-11-19 11:56 ` Christian Johansson
2018-11-14 8:05 ` Michael Albinus
2018-10-25 5:03 ` Christian Johansson
2022-04-24 14:22 ` Lars Ingebrigtsen
2022-04-24 15:00 ` Christian Johansson
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=112C9286-C8BE-4869-ACFC-07905FFD6A44@cvj.se \
--to=christian@cvj.se \
--cc=33135@debbugs.gnu.org \
--cc=alan@idiocy.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).