all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org, vibhavp@gmail.com
Subject: Re: feature/asan-gc-poisoning 5c653d3ec9: Add support for additional memory checks using AddressSanitizer.
Date: Wed, 30 Nov 2022 15:41:32 +0200	[thread overview]
Message-ID: <83a648lfub.fsf@gnu.org> (raw)
In-Reply-To: <87h6yhujha.fsf@yahoo.com> (message from Po Lu on Wed, 30 Nov 2022 12:58:09 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: Vibhav Pant <vibhavp@gmail.com>
> Date: Wed, 30 Nov 2022 12:58:09 +0800
> 
> Vibhav Pant <vibhavp@gmail.com> writes:
> 
> >     Add support for additional memory checks using AddressSanitizer.
> >     
> >     When Emacs is compiled with AddressSanitizer support, enable
> >     poisoning/unpoisoning freed/unused Lisp objects and other internal
> >     memory management structures. If enabled, this will mark freed bytes
> >     that have been put on free lists for future use, and initially
> >     allocated memory blocks/chunks as "poisoned", triggering an ASan error
> >     if they are accessed improperly. Structures are unpoisoned when they
> >     have been taken off their respective free lists.

To be more useful, this should be mentioned in etc/DEBUG, where we describe
how to build and run Emacs with memory-debugging facilities.

Thanks.



      reply	other threads:[~2022-11-30 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166975768364.28465.5012752085318372072@vcs2.savannah.gnu.org>
     [not found] ` <20221129213444.5CC36C009EC@vcs2.savannah.gnu.org>
2022-11-30  4:58   ` feature/asan-gc-poisoning 5c653d3ec9: Add support for additional memory checks using AddressSanitizer Po Lu
2022-11-30 13:41     ` Eli Zaretskii [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=83a648lfub.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=vibhavp@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 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.