From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 56108@debbugs.gnu.org
Subject: bug#56108: 29.0.50; ASAN use-after-free in re_match_2_internal
Date: Thu, 23 Jun 2022 07:53:29 +0200 [thread overview]
Message-ID: <3146c990-63d9-4aa5-ab78-7bae2b7d6cd5@Spark> (raw)
In-Reply-To: <83sfnwisbb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On 22. Jun 2022, 18:20 +0200, Eli Zaretskii <eliz@gnu.org>, wrote:
> >
> > I think the next step is to add the missing freeze_pattern calls and
> > see if that fixes the problem?
I think the missing freezes are 100% a bug, and they should be fixed.
Do you want to do that or should I?
(BTW, I just now noticed the "->buf" at the end of the "bufp = &compile_pattern (regexp,...)" that I complained about. That explains it. Nice :-/.)
Another side question, if I may: Have you perhaps heard of someone producing a static call graph for Emacs, or better yet, specific functions in Emacs? Maybe using objdump -D or something similar?
[-- Attachment #2: Type: text/html, Size: 1245 bytes --]
next prev parent reply other threads:[~2022-06-23 5:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 14:07 bug#56108: 29.0.50; ASAN use-after-free in re_match_2_internal Gerd Möllmann
2022-06-20 19:09 ` Eli Zaretskii
2022-06-22 8:13 ` Gerd Möllmann
2022-06-22 13:38 ` Eli Zaretskii
2022-06-22 14:10 ` Gerd Möllmann
2022-06-22 14:24 ` Eli Zaretskii
2022-06-22 15:11 ` Gerd Möllmann
2022-06-22 16:19 ` Eli Zaretskii
2022-06-23 5:53 ` Gerd Möllmann [this message]
2022-06-23 6:57 ` Eli Zaretskii
2022-06-23 7:17 ` Eli Zaretskii
2022-06-23 21:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-24 5:55 ` Eli Zaretskii
2022-06-24 6:01 ` Gerd Möllmann
2022-06-24 9:35 ` Gerd Möllmann
2022-06-24 15:40 ` Eli Zaretskii
2022-06-25 9:18 ` Eli Zaretskii
2022-06-27 13:26 ` Eli Zaretskii
2022-06-27 13:29 ` Gerd Möllmann
2022-06-23 8:24 ` Gerd Möllmann
2022-06-23 8:37 ` Eli Zaretskii
2022-06-23 8:49 ` Gerd Möllmann
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3146c990-63d9-4aa5-ab78-7bae2b7d6cd5@Spark \
--to=gerd.moellmann@gmail.com \
--cc=56108@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).