From: Roger Phillips <heidegg@hotmail.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Getting more info about a heap corruption
Date: Wed, 14 Jun 2023 07:21:06 +0000 [thread overview]
Message-ID: <SJ0PR06MB86417146389FD199D4F76B6CAA5AA@SJ0PR06MB8641.namprd06.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
Greetings,
currently I'm analysing a number of heap corruptions in a large application which usually results in a coredump and one of these malloc_printerr :
https://elixir.bootlin.com/glibc/glibc-2.31/source/malloc/malloc.c#L3744
malloc.c - malloc/malloc.c - Glibc source code (glibc-2.31) - Bootlin<https://elixir.bootlin.com/glibc/glibc-2.31/source/malloc/malloc.c#L3744>
Elixir Cross Referencer - Explore source code in your browser - Particularly useful for the Linux kernel and other low-level projects in C/C++ (bootloaders, C libraries...)
elixir.bootlin.com
Problem is that variables needed for this check like victim, bck and next are optimized out and thus not accessible in gdb. Only av and its contents are accessible. I cannot use asan binaries as it is a production test. Changing environment variables is possible though.
So can you tell me if there is any sort of debugging functionality in glibc-2.31 that will show me those missing variables or narrow down the corrupted chunk?
Regards
next reply other threads:[~2023-06-14 7:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 7:21 Roger Phillips [this message]
2023-06-14 9:24 ` Florian Weimer
2023-06-14 10:13 ` Roger Phillips
2023-06-14 10:17 ` Florian Weimer
2023-06-14 10:21 ` Roger Phillips
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=SJ0PR06MB86417146389FD199D4F76B6CAA5AA@SJ0PR06MB8641.namprd06.prod.outlook.com \
--to=heidegg@hotmail.com \
--cc=libc-help@sourceware.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 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).