From: Eli Zaretskii <eliz@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: 65837@debbugs.gnu.org
Subject: bug#65837: 30.0.50; Debugger in non-main threads
Date: Sat, 09 Sep 2023 14:14:20 +0300 [thread overview]
Message-ID: <83bkebvbsj.fsf@gnu.org> (raw)
In-Reply-To: <m21qf71zcn.fsf@gmail.com> (message from Helmut Eller on Sat, 09 Sep 2023 11:15:52 +0200)
> From: Helmut Eller <eller.helmut@gmail.com>
> Date: Sat, 09 Sep 2023 11:15:52 +0200
>
> When the debugger is entered in a non-main thread, like so
>
> emacs -Q --eval '(make-thread (lambda() (debug)))'
>
> Then debugger-quit doesn't work as usual, instead it prints
>
> debugger-quit: No catch for tag: top-level, nil
>
> or it prints
>
> Back to top level
>
> but doesn't actually close the debugger window.
>
> Also, debugger-continue doesn't work as usual, instead it sometimes prints:
>
> debugger-continue: No catch for tag: exit, nil
>
> sometimes it prints:
>
> Continuing.
>
> without deleting the debugger window, sometimes it manages to leave the
> debugger.
>
> If Emacs is started with "emacs -Q -nw" then the behaviour seems to be a
> bit more uniform, but equally useless.
Yes, error handling in non-main threads is generally rudimentary and
barely useful. For example, if a thread signals an error, it simply
silently exits and leaves the error form in a variable that can be
accessed via thread-last-error. AFAIR, it is not trivial to improve
the thread error handling significantly, but patches are welcome, of
course.
next prev parent reply other threads:[~2023-09-09 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 9:15 bug#65837: 30.0.50; Debugger in non-main threads Helmut Eller
2023-09-09 11:14 ` Eli Zaretskii [this message]
2023-09-09 15:35 ` Helmut Eller
2023-09-09 15:57 ` Eli Zaretskii
2023-09-09 16:23 ` Helmut Eller
2023-09-09 16:46 ` Eli Zaretskii
2023-09-09 17:24 ` Helmut Eller
2023-09-09 17:37 ` Eli Zaretskii
2023-09-09 18:29 ` Helmut Eller
2023-09-09 18:34 ` Eli Zaretskii
2023-09-09 18:50 ` Helmut Eller
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=83bkebvbsj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65837@debbugs.gnu.org \
--cc=eller.helmut@gmail.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.