From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 45117@debbugs.gnu.org
Subject: bug#45117: 28.0.50; process-send-string mysteriously exiting non-locally when called from timer
Date: Wed, 09 Dec 2020 11:24:47 +0000 [thread overview]
Message-ID: <87im9b2pds.fsf@gmail.com> (raw)
In-Reply-To: <83360g6xlt.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 08 Dec 2020 19:01:18 +0200")
[ We've been CC-ing bug-gnu-emacs@gnu.org for a while. My fault, the
typical CC blunder. Wonder how debbugs was dealing with that so
gracefully tho. ]
Eli Zaretskii <eliz@gnu.org> writes:
>> From: João Távora <joaotavora@gmail.com>
>> Cc: bug-gnu-emacs@gnu.org
>> Date: Tue, 08 Dec 2020 15:56:49 +0000
>>
>> > Can you elaborate on the evidence you found of this non-local exit?
>>
>> It was evidenced by M-x trace-function process-send-string RET and also
>> by substituting the snippet I posted earlier with:
> few places we call sys_longjmp, and when it breaks, show the C and
> Lisp backtrace from there.
Right, so I got this setup, compiled Emacs 27.1 with all debugging
flags. I can reproduce it, and even with GDB attached, great. The
problem is the breakpoints.
If I set breakpoints at _all_ places where we call sys_longjmp(), I risk
tearing down my X, which I did a couple of times.
So I skip those "dangerous" breakpoints. I'm guessing one of the
interesting loci to break is unwind_to_catch in eval.c. Of course that
gets called every dang time a signal is thrown, so it's hard for me to
catch the precise situation, even if I set up nicely and then call M-x
redraw-display, and only then enable the breakpoint.
It breaks near immediately, and the `bt` output I get is always from
some other function that expectedly signalled an error as part of its
normal control flow. (Yeah, maybe I shouldn't be using signals for
normal control flow, but that's another matter.)
So:
1. I have to find a way to set the unwind_to_catch() breakpoint
conditional on some Elisp/near-elisp context, in this case something
inside the Elisp function sly-net-send() or Fprocess_send_string.
Do you think setting a silly global in Fprocess_send_string() and
then checking that as the breakpoint condition would be a good idea?
Where would I reset the flag? Is there some C-version of
"unwind-protect"?
2. The mysterious long jump may be coming from some other place. I
enabled a breakpoint in the sys_longjmp call in
quit_throw_to_read_char(), but that's not it, I can reproduce the
error and it doesn't break there. Then there are some in image.c
loci that I don't think matter much and the one in alloc.c which
freezes my X.
3. I set up one of those "tracer" breakpoints for the that you once
showed me (how did that go?) They're going to make a LOT of noise,
but at least we should be able to register the correct
unwind_to_catch() context.
João
next prev parent reply other threads:[~2020-12-09 11:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 11:44 bug#45117: 28.0.50; process-send-string mysteriously exiting non-locally when called from timer João Távora
2020-12-08 15:39 ` Eli Zaretskii
2020-12-08 15:56 ` João Távora
2020-12-08 17:01 ` Eli Zaretskii
2020-12-08 17:05 ` João Távora
2020-12-09 11:24 ` João Távora [this message]
2020-12-09 15:33 ` Eli Zaretskii
2020-12-10 15:00 ` João Távora
2020-12-10 15:23 ` Eli Zaretskii
2020-12-10 16:15 ` João Távora
2020-12-10 16:29 ` João Távora
2020-12-10 17:20 ` Dmitry Gutov
2020-12-10 17:51 ` Stefan Monnier
2020-12-10 18:05 ` João Távora
2020-12-10 18:37 ` Stefan Monnier
2020-12-10 18:48 ` Eli Zaretskii
2020-12-10 18:50 ` João Távora
2020-12-10 19:44 ` Eli Zaretskii
2020-12-10 19:47 ` João Távora
2020-12-10 19:55 ` Eli Zaretskii
2020-12-10 19:58 ` João Távora
2020-12-10 20:14 ` Eli Zaretskii
2020-12-10 20:15 ` João Távora
2020-12-10 20:37 ` Dmitry Gutov
2020-12-10 19:46 ` Stefan Monnier
2020-12-10 20:12 ` João Távora
2020-12-10 20:43 ` Stefan Monnier
2020-12-10 20:55 ` Dmitry Gutov
2020-12-10 22:48 ` Stefan Monnier
2020-12-10 21:16 ` João Távora
2020-12-10 22:58 ` João Távora
2020-12-11 7:31 ` Eli Zaretskii
2020-12-11 14:31 ` Stefan Monnier
2020-12-11 14:40 ` Eli Zaretskii
2020-12-11 14:43 ` João Távora
2020-12-11 14:41 ` João Távora
2020-12-11 14:50 ` Stefan Monnier
2020-12-13 23:19 ` João Távora
2020-12-14 0:35 ` Stefan Monnier
2020-12-10 16:41 ` 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=87im9b2pds.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=45117@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.