"Alex V. Koval" <[email protected]> writes: > Hi Michael,
Hi Alex, > I've enabled trace and tried it. After waiting for 30 minutes, trace was > still saving and file did not open, so I've interrupted it with C-g, but > I think it has collected enough information for this issue. > > Please have a quick look when you have time on this, and may be post > some advice for bbatsov on how to workaround this, but since its not > purely tramp issue and since I alredy fixed it for myself, there is no > urgency on this. I see in the traces that you have interrupted Tramp, but this isn't sufficient. I need also the backtrace at this time. Could you pls apply the appended patch to tramp.el, and rerun the test? The trace shall tell us then, where the problem happened. > WBR, > Alex Best regards, Michael.
*** /tmp/ediffYq65Fx 2019-03-12 17:42:18.901158753 +0100 --- /home/albinus/src/tramp-2-3-stable/lisp/tramp.el 2019-03-12 17:41:58.812368593 +0100 *************** *** 2235,2240 **** --- 2235,2241 ---- ;; Trace that somebody has interrupted the operation. ((debug quit) (let (tramp-message-show-message) + (tramp-backtrace v) (tramp-message v 1 "Interrupt received in operation %s" (cons operation args)))
_______________________________________________ Tramp-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/tramp-devel
