unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 56095@debbugs.gnu.org
Subject: bug#56095: 29.0.50; nsterm.m, use after free
Date: Mon, 20 Jun 2022 09:22:32 +0800	[thread overview]
Message-ID: <87r13kw2lj.fsf@yahoo.com> (raw)
In-Reply-To: <m2wndciv7l.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Sun, 19 Jun 2022 16:28:14 +0200")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> So, I'm trying Emacs on MacOS now, get some non-reproducible
> crashes, built master with ASAN, and the first thing it found is this:
>
> ==61522==ERROR: AddressSanitizer: heap-use-after-free on address 0x00012d7deb90 at pc 0x0001008c1514 bp 0x00016fdf7230 sp 0x00016fdf7228
> WRITE of size 8 at 0x00012d7deb90 thread T0
> ==61522==WARNING: Can't read from symbolizer at fd 25
> ==61522==WARNING: Can't read from symbolizer at fd 26
> ==61522==WARNING: Can't read from symbolizer at fd 27
> ==61522==WARNING: Can't read from symbolizer at fd 28
> ==61522==WARNING: Failed to use and restart external symbolizer!
>     #0 0x1008c1510 in wset_vertical_scroll_bar+0x4c (/Users/gerd/repos/emacs/src/emacs:arm64+0x1008c1510)
>     #1 0x1008c19a0 in -[EmacsScroller judge]+0x360 (/Users/gerd/repos/emacs/src/emacs:arm64+0x1008c19a0)
>     #2 0x1008d641c in ns_judge_scroll_bars+0x224 (/Users/gerd/repos/emacs/src/emacs:arm64+0x1008d641c)
>     #3 0x1000fa4ec in redisplay_internal+0x4ca4 (/Users/gerd/repos/emacs/src/emacs:arm64+0x1000fa4ec)
> ...

Isn't that a bug, since scroll bars should only be judged for windows
that are still reachable?





  reply	other threads:[~2022-06-20  1:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 14:28 bug#56095: 29.0.50; nsterm.m, use after free Gerd Möllmann
2022-06-20  1:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-06-20  6:02   ` Gerd Möllmann
2022-06-20 10:21     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-21 14:25       ` Gerd Möllmann
2022-06-21 15:43         ` Eli Zaretskii
2022-06-22  5:26           ` Gerd Möllmann
2022-06-22  9:19             ` Gerd Möllmann
2022-06-22 13:21               ` Eli Zaretskii
2022-06-22 13:43                 ` Gerd Möllmann
2022-06-22  1:30         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-22 13:53           ` Eli Zaretskii
2022-06-22 14:15             ` Gerd Möllmann
2022-06-22 16:14               ` Eli Zaretskii
     [not found] <27290ad8-4f51-41e5-9317-46e4b3c5dd6c@Spark>
2022-06-19 17:32 ` bug#56095: Patch Gerd Möllmann
2022-06-19 22:51   ` bug#56095: 29.0.50; nsterm.m, use after free Lars Ingebrigtsen

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=87r13kw2lj.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56095@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=luangruo@yahoo.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 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).