unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 73838@debbugs.gnu.org
Subject: bug#73838: 31.0.50; Problems in note_mouse_highlight if -nw
Date: Thu, 17 Oct 2024 13:44:52 +0300	[thread overview]
Message-ID: <867ca7ovob.fsf@gnu.org> (raw)
In-Reply-To: <m234kvnrda.fsf@gmail.com> (message from Gerd Möllmann on Thu, 17 Oct 2024 09:03:13 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 73838@debbugs.gnu.org
> Date: Thu, 17 Oct 2024 09:03:13 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > If that's not what you are suggesting, I
> > wonder what is wrong with the current code that we need to make
> > changes which are basically half-solutions.  If the problem is access
> > to unrelated memory, that is easy to fix by just adding enough slack
> > to tty_output definition, for example.
> 
> You mean by making sizeof (struct tty_output) == sizeof (ns_output) in
> my case, and let it go? Bloodcurdlingly horrible! I don't even want to
> think about it.

Why is it a problem to add some dummy buffer to a struct? what's so
horrible about that?  The reason is to let ASAN build run without
false positives.

Alternatively, cannot you tell ASAN in some way that this code is
okay?

> I'm think I understand that. And I can understand that you are not
> interested unless a "grander" solution is available, maybe something
> like the "base class" approach I tried to describe above. So be it.
> 
> I think you can as well close this bug as wontfix. It's unlikely that
> I'll work in the direction you would like to see in the forseeable
> future.

Understood.





  reply	other threads:[~2024-10-17 10:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 10:47 bug#73838: 31.0.50; Problems in note_mouse_highlight if -nw Gerd Möllmann
2024-10-16 14:19 ` Gerd Möllmann
2024-10-16 15:38   ` Eli Zaretskii
2024-10-16 16:56     ` Gerd Möllmann
2024-10-16 18:30       ` Eli Zaretskii
2024-10-16 19:03         ` Gerd Möllmann
2024-10-17  4:06           ` Eli Zaretskii
2024-10-17  5:07             ` Gerd Möllmann
2024-10-17  5:48               ` Eli Zaretskii
2024-10-17  7:03                 ` Gerd Möllmann
2024-10-17 10:44                   ` Eli Zaretskii [this message]
2024-10-17 12:12                     ` Gerd Möllmann
2024-10-17 10:46                   ` Eli Zaretskii
2024-10-17 12:39                     ` Gerd Möllmann
2024-10-19  3:50                       ` Gerd Möllmann
2024-10-19  8:00                         ` Gerd Möllmann
2024-10-16 15:27 ` Eli Zaretskii
2024-10-16 16:41   ` 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=867ca7ovob.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73838@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.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).