From: Glenn Washburn <development@efficientek.com>
To: Daniel Kiper <dkiper@net-space.pl>, grub-devel@gnu.org
Cc: Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/3] Fixes and enhancements for memory debugging
Date: Tue, 15 Feb 2022 12:36:40 -0600 [thread overview]
Message-ID: <cover.1644949742.git.development@efficientek.com> (raw)
The first patch supercedes a patch sent earlier of the same subject. I've
removed the #undef if --mm-debug is not passwed to configure. The idea is
that even if --mm-debug is not passed to configure, the user should still
be able to enable memory debugging by passing -DMM_DEBUG in CFLAGS.
The second patch I found useful in dumping the memory allocation state from
a module.
And the third patch is a bug fix, without which enabling memory debugging
leads to a certain infinite recursion crash (when also enabling grub_mm_debug).
As an aside, this leads me to believe that no one has used this feature in
a very long time (and is not currently using it).
Glenn
Glenn Washburn (3):
configure: Properly handle MM_DEBUG
mm: Export grub_mm_dump and grub_mm_dump_free
mm: Temporarily disable grub_mm_debug while calling grub_vprintf in
grub_printf
config.h.in | 4 ++++
configure.ac | 6 ++++--
grub-core/kern/misc.c | 19 +++++++++++++++++++
include/grub/mm.h | 4 ++--
4 files changed, 29 insertions(+), 4 deletions(-)
--
2.27.0
next reply other threads:[~2022-02-15 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 18:36 Glenn Washburn [this message]
2022-02-15 18:36 ` [PATCH 1/3] configure: Properly handle MM_DEBUG Glenn Washburn
2022-02-22 18:00 ` Daniel Kiper
2022-02-15 18:36 ` [PATCH 2/3] mm: Export grub_mm_dump and grub_mm_dump_free Glenn Washburn
2022-02-22 18:03 ` Daniel Kiper
2022-02-25 21:04 ` Glenn Washburn
2022-03-02 20:51 ` Daniel Kiper
2022-02-15 18:36 ` [PATCH 3/3] mm: Temporarily disable grub_mm_debug while calling grub_vprintf in grub_printf Glenn Washburn
2022-02-22 18:07 ` Daniel Kiper
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=cover.1644949742.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@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.
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.