From: Eli Zaretskii <eliz@gnu.org>
To: Han Boetes <han@boetes.org>
Cc: 51689@debbugs.gnu.org
Subject: bug#51689: emacs
Date: Sat, 20 Nov 2021 17:15:12 +0200 [thread overview]
Message-ID: <83ilwmsvsv.fsf@gnu.org> (raw)
In-Reply-To: <YZkNVFiynVNhCzD0@boetes.org> (message from Han Boetes on Sat, 20 Nov 2021 15:59:32 +0100)
> Date: Sat, 20 Nov 2021 15:59:32 +0100
> From: Han Boetes <han@boetes.org>
> Cc: 51689@debbugs.gnu.org
>
> Breakpoint 3, Fsignal (error_symbol=XIL(0xe100), data=XIL(0x9c9423a4e03)) at eval.c:1790
> 1790 if (NILP (error_symbol) && NILP (data))
> void-variable
> (byte-compile-verbose)
This is OK, but this is not the call to 'signal' that we are looking
for. As I said in my instructions:
> > When the breakpoint breaks, look at the error_symbol and data printed
> > by GDB; if the symbol are not "void-function", type "continue" at
> > GDB's prompt to run Emacs further. When you eventually get symbol as
> > "void-function" and data that mentions regexp-opt-group, type:
> >
> > (gdb) thread apply all bt
In the above you have void-variable as error_symbol and the data does
not mention regexp-opt-group. So you need to type "continue" until
you hit this breakpoint with the correct conditions, and then produce
the backtrace.
Thanks.
next prev parent reply other threads:[~2021-11-20 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 16:44 bug#51689: emacs Han Boetes
2021-11-08 18:15 ` Eli Zaretskii
2021-11-14 19:26 ` Eli Zaretskii
2021-11-14 21:20 ` Han Boetes
2021-11-15 12:33 ` Eli Zaretskii
2021-11-16 9:22 ` Han Boetes
2021-11-16 13:24 ` Eli Zaretskii
2021-11-17 17:45 ` Eli Zaretskii
2021-11-17 20:45 ` Han Boetes
2021-11-17 21:41 ` Han Boetes
2021-11-18 7:13 ` Eli Zaretskii
2021-11-19 22:18 ` Han Boetes
2021-11-20 9:36 ` Eli Zaretskii
2021-11-20 14:59 ` Han Boetes
2021-11-20 15:15 ` Eli Zaretskii [this message]
[not found] ` <YZljMydhnoE0Di4p@boetes.org>
2021-11-21 6:31 ` 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=83ilwmsvsv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51689@debbugs.gnu.org \
--cc=han@boetes.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.