From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Gregor Zattler <telegraph@gmx.net>, 75459@debbugs.gnu.org
Subject: bug#75459: 31.0.50; scratch-igc: Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432
Date: Thu, 09 Jan 2025 15:52:10 +0100 [thread overview]
Message-ID: <m234hs2g6d.fsf@gmail.com> (raw)
In-Reply-To: <m27c742gz9.fsf@gmail.com> ("Gerd Möllmann"'s message of "Thu, 09 Jan 2025 15:34:50 +0100")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Date: Thu, 09 Jan 2025 12:19:26 +0100
>>> From: Gregor Zattler via "Bug reports for GNU Emacs,
>>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>>
>>> Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6,
>>> backtrace_limit=backtrace_limit@entry=2147483647) at
>>> ./src/emacs.c:432
>>> 432 {
>>> #0 terminate_due_to_signal (sig=sig@entry=6,
>>> backtrace_limit=backtrace_limit@entry=2147483647) at
>>> ./src/emacs.c:432
>>> #1 0x00005555555b72db in die (msg=msg@entry=0x5555559cedde
>>> "CHAR_TABLE_P (obj)", file=file@entry=0x5555559b0565 "character.h",
>>> line=line@entry=597) at ./src/alloc.c:8377
>>> #2 0x00005555555b6acd in char_table_translate (obj=Python Exception
>>> <class 'gdb.error'>: value has been optimized out
>>> , ch=32) at ./src/character.h:597
>>> #3 0x00005555557d99a0 in re_match_2_internal (bufp=0x5555560fd6a0
>>> <searchbufs+2912>, bufp@entry=0x5eb92b3c6c43c900, string1=0x0,
>>> string1@entry=0x555557025101 "\377\377\377\377\377\377\377\001",
>>> size1=0, string2=0x5555570251b0 "#-*- mode: Org; indent-tabs-mode:
>>> nil; coding: utf-8-unix -*-\n#+STARTUP: hidestars\n#+STARTUP:
>>> odd\n;#+STARTUP: overview\n#+STARTUP: showeverything\n#+SEQ_TODO:
>>> TODO(t) INPROGRESS(i@/@) WAITING(w@/@) VER"..., size2=93674,
>>> size2@entry=93825020464468, pos=43986, regs=<optimized out>,
>>> stop=<optimized out>) at ./src/regex-emacs.c:4553
>>
>> bufp->translate is not protected from GC?
>
> Thanks!
>
> I think the bufp should come from a regexp_cache entry that looking_at_1
> gets from compile_pattern, and passes to re_match_2
>
> i = re_match_2 (&cache_entry->buf, (char *) p1, s1, (char *) p2, s2,
>
> compile_pattern chooses an entry from searchbuf_head, fills it out and
> so on. I think searchbuf_head refers to entries in searchbuf, which is
> an array of regexp_cache. And in syms_of_search we have
>
> for (int i = 0; i < REGEXP_CACHE_SIZE; ++i)
> {
> staticpro (&searchbufs[i].regexp);
> staticpro (&searchbufs[i].f_whitespace_regexp);
> staticpro (&searchbufs[i].syntax_table);
> }
>
> That doesn't look sufficient, at least for igc, don't know about the old
> gc. I'll see what must be added there, bufp->translate is certainly
> among that, but maybe there are others.
Done, but what Pip says.
prev parent reply other threads:[~2025-01-09 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 11:19 bug#75459: 31.0.50; scratch-igc: Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432 Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 13:03 ` Eli Zaretskii
2025-01-09 14:34 ` Gerd Möllmann
2025-01-09 14:47 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 15:32 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 16:14 ` Gerd Möllmann
2025-01-09 19:27 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-09 22:29 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-10 4:52 ` Gerd Möllmann
2025-01-09 14:52 ` Gerd Möllmann [this message]
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=m234hs2g6d.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=75459@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=telegraph@gmx.net \
/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.