From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: emacs-devel@gnu.org
Subject: Debugging Emacs with threads
Date: Sun, 11 Dec 2016 18:26:12 +0200 [thread overview]
Message-ID: <83inqqe8kb.fsf@gnu.org> (raw)
There's a nasty issue that people who debug Emacs with threads need to
be aware of.
When Emacs stops due to a breakpoint, the thread that is the current
one is in sync between GDB and Emacs. IOW, the current_thread
variable describes the same thread on which GDB commands will act.
But as soon as you say something like "thread 1" at the GDB prompt,
this synchronization is lost: GDB acts on the thread you specified,
while current_thread is still pointing at the thread which was the
current one when Emacs stopped.
The result of this is that invoking functions in Emacs will likely
crash, because thread-specific variables used by Emacs are incorrect
for the thread whose stack GDB will use to create the call-stack frame
for the function it calls. In particular, xbacktrace will definitely
crash. And since src/.gdbinit automatically invokes xbacktrace when
you type "bt", any "bt" issued when the threads mismatch will ruin the
debugging session.
It would be good to protect xbacktrace from this, and avoid calling
functions in Emacs in this situation. Unfortunately, I couldn't find
any way of gleaning the OS thread ID from the GDB thread number.
Maybe Tom, who knows a lot about GDB, could help, or someone else
might have an idea that we then could implement in .gdbinit?
TIA
next reply other threads:[~2016-12-11 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 16:26 Eli Zaretskii [this message]
2016-12-11 16:43 ` Debugging Emacs with threads Andreas Schwab
2016-12-11 17:37 ` Eli Zaretskii
2016-12-11 18:04 ` Andreas Schwab
2016-12-11 18:12 ` Eli Zaretskii
2016-12-12 3:07 ` Ken Raeburn
2016-12-12 3:18 ` Ken Raeburn
2016-12-12 17:38 ` Eli Zaretskii
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=83inqqe8kb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tom@tromey.com \
/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.