all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs without threads
Date: Thu, 14 Dec 2023 15:01:23 +0200	[thread overview]
Message-ID: <83edfpq6os.fsf@gnu.org> (raw)
In-Reply-To: <877clh6jky.fsf@ledu-giraud.fr> (message from Manuel Giraud on Thu, 14 Dec 2023 13:43:09 +0100)

> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: emacs-devel@gnu.org
> Date: Thu, 14 Dec 2023 13:43:09 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > What do you mean by "without thread support at all", and how is it
> > different from what you get with --without-threads?
> 
> I mean that Emacs won't be able to start any thread (for example via
> pthread_* functions).

That's what --without-threads does.

> I thought that --without-threads only removed the Lisp support for
> threads because, from a debugging session, Emacs does seem to
> continue to start threads.

The threads you see under a debugger are not Lisp threads, they are
threads started by GTK and other libraries we link against.  You
cannot disable them, except by building Emacs without those libraries
(I think just without GTK should do, if you are on GNU/Linux).

> (FWIW, I want this to simplify debugging because on my machine I cannot
> make GDB to switch to the correct thread

How come?

> or to continue running other threads)

Why would you need to do that?



  reply	other threads:[~2023-12-14 13:01 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 [this message]
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
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=83edfpq6os.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.