From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: Emacs without threads
Date: Fri, 22 Dec 2023 16:54:18 +0200 [thread overview]
Message-ID: <83cyuyfftx.fsf@gnu.org> (raw)
In-Reply-To: <87cyuy9u0s.fsf@ledu-giraud.fr> (message from Manuel Giraud on Fri, 22 Dec 2023 15:44:19 +0100)
> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: michael.albinus@gmx.de, emacs-devel@gnu.org
> Date: Fri, 22 Dec 2023 15:44:19 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > And "emacs" in the above "M-x gdb" command is a shell script that
> > starts Emacs via dbus-launch? If not, i.e. if "emacs" is the Emacs
> > binary itself, then how is dbus-launch involved in this?
>
> No it is not the sub emacs (into GDB) that calls dbus-launch, it's the
> top level Emacs:
>
> - my .xsession launches "exec dbus-launch --sh-syntax
> --exit-with-x11 emacs"
>
> - Now I am in Emacs, I go to Emacs src directory and I do 'M-x
> gdb'
>
> - This gdb session launches another sub emacs to be debugged
So only the Emacs which runs "M-x gdb" us launched from dbus-launch,
and the Emacs being debugged is run directly by GDB? Then I don't
understand why you see any threads during debugging: GDB only shows
threads of the program being debugged.
next prev parent reply other threads:[~2023-12-22 14:54 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
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 [this message]
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
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=83cyuyfftx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=manuel@ledu-giraud.fr \
--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).