From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs without threads
Date: Sat, 16 Dec 2023 15:13:29 +0200 [thread overview]
Message-ID: <83bkaqmgsm.fsf@gnu.org> (raw)
In-Reply-To: <874jgjsh26.fsf@ledu-giraud.fr> (message from Manuel Giraud on Fri, 15 Dec 2023 14:58:57 +0100)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: emacs-devel@gnu.org
> Date: Fri, 15 Dec 2023 14:58:57 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > If you start GDB from the shell prompt, not from Emacs, does this
> > happen then as well? If not, this could be some bug in gdb-mi.el.
>
> … Thank you for suggesting it because I have tried with "gdb ./emacs"
> from a xterm and I am not able to reproduce this lock. I have also
> tried with 'M-x gud-gdb' and I also ended up stuck. So there might be
> something at play in gdb-mi.el.
Strange, gdb-mi.el is not supposed to cause any threads anywhere.
Does anyone see something like that on GNU/Linux?
> FWIW, I have also noticed that even though I have closed the stuck Emacs
> and delete the *gud* Emacs process. The system process for GDB and
> Emacs are still there and in weird states. ps gives me the following
> STAT:
>
> - GDB is DlL which means: in uninterruptible wait, ld.so has
> syscall pinning, libc.so has syscall pinning
>
> - Emacs is TXlL which means: stopped process, being traced or
> debugged, ld.so has syscall pinning, libc.so has syscall pinning
Attaching a GDB to each one of those and posting a backtrace might
give us some ideas.
next prev parent reply other threads:[~2023-12-16 13:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 10:36 Emacs without threads Manuel Giraud via Emacs development discussions.
2023-12-14 11:16 ` Eli Zaretskii
2023-12-14 12:43 ` Manuel Giraud via Emacs development discussions.
2023-12-14 13:01 ` Eli Zaretskii
2023-12-14 14:12 ` Manuel Giraud via Emacs development discussions.
2023-12-14 16:34 ` Eli Zaretskii
2023-12-15 11:08 ` Manuel Giraud via Emacs development discussions.
2023-12-15 12:11 ` Eli Zaretskii
2023-12-15 13:58 ` Manuel Giraud via Emacs development discussions.
2023-12-16 13:13 ` Eli Zaretskii [this message]
2023-12-16 19:13 ` Manuel Giraud via Emacs development discussions.
2023-12-16 19:26 ` Eli Zaretskii
2023-12-17 18:43 ` Manuel Giraud via Emacs development discussions.
2023-12-18 3:24 ` Eli Zaretskii
2023-12-18 6:53 ` Manuel Giraud via Emacs development discussions.
2023-12-18 17:43 ` Eli Zaretskii
2023-12-22 9:20 ` Michael Albinus
2023-12-22 11:48 ` Eli Zaretskii
2023-12-22 12:11 ` Michael Albinus
2023-12-22 13:55 ` Manuel Giraud via Emacs development discussions.
2023-12-22 14:28 ` Eli Zaretskii
2023-12-22 14:44 ` Manuel Giraud via Emacs development discussions.
2023-12-22 14:54 ` Eli Zaretskii
2023-12-22 14:45 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bkaqmgsm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.