From: Stephen Berman <stephen.berman@gmx.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>,
Casey Connor <emacsbugs@caseyconnor.org>,
60796@debbugs.gnu.org
Subject: bug#60796: 27.1; Opening file ending in .sh inside a directory ending in .deb causes hang/100% thread usage
Date: Sun, 15 Jan 2023 17:16:10 +0100 [thread overview]
Message-ID: <87cz7fhiyd.fsf@gmx.net> (raw)
In-Reply-To: <87mt6jok46.fsf@gmx.de> (Michael Albinus's message of "Sun, 15 Jan 2023 17:09:13 +0100")
On Sun, 15 Jan 2023 17:09:13 +0100 Michael Albinus <michael.albinus@gmx.de> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
> Hi Stephen,
>
>>> Note that there was a similar report, bug#30293, which was fixed in
>>> Emacs 27. So in general the scenario shall work. If possible, I'd like
>>> to see a backtrace for the Emacs 27 case.
>>
>> Do you mean from gdb? If so, see below.
>>
>>> Note also, that there were autoload problems in the past for
>>> tramp-archive.el (which should be fixed now). So would it work in your
>>> case, if you call instead
>>>
>>> $ emacs -Q -l tramp-archive test.sh
>>
>> This doesn't prevent the freeze and 100% core usage for me. I attached
>> the emacs process to gdb and append the backtrace below. If this is not
>> what you want, or if you want me to execute specific gdb commands,
>> please let me know what I should do.
>
> Hmm, no, it doesn't tell me anything. Emacs is stuck somewhere in alloc.
>
> What I've hoped is that you could stop Emacs by hitting C-g, and show a
> Lisp backtrace.
No, Emacs is totally locked up and repeatedly hitting C-g or ESC doesn't
help.
Steve Berman
next prev parent reply other threads:[~2023-01-15 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 23:19 bug#60796: 27.1; Opening file ending in .sh inside a directory ending in .deb causes hang/100% thread usage Casey Connor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 3:15 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 7:21 ` Eli Zaretskii
2023-01-14 7:43 ` Casey Connor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-14 7:56 ` Eli Zaretskii
2023-01-14 11:20 ` Stephen Berman
2023-01-14 18:53 ` Casey Connor via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-15 15:15 ` Michael Albinus
2023-01-15 15:14 ` Michael Albinus
2023-01-15 16:00 ` Stephen Berman
2023-01-15 16:09 ` Michael Albinus
2023-01-15 16:16 ` Stephen Berman [this message]
2023-01-15 16:21 ` Michael Albinus
2023-01-15 16:34 ` Stephen Berman
2023-01-15 16:47 ` Michael Albinus
2023-01-15 17:04 ` Stephen Berman
2023-01-15 18:25 ` Michael Albinus
2023-01-15 19:05 ` Stephen Berman
2023-01-14 8:47 ` Michael Albinus
2023-01-15 7:18 ` Jean Louis
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=87cz7fhiyd.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=60796@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=emacsbugs@caseyconnor.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).