From: Roger Phillips <heidegg@hotmail.com>
To: Florian Weimer <fweimer@redhat.com>,
Roger Phillips via Libc-help <libc-help@sourceware.org>
Subject: Re: Getting more info about a heap corruption
Date: Wed, 14 Jun 2023 10:13:12 +0000 [thread overview]
Message-ID: <SJ0PR06MB8641391BD560EDBD3798022CAA5AA@SJ0PR06MB8641.namprd06.prod.outlook.com> (raw)
In-Reply-To: <87a5x2s8es.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Thanks for the answer! Do you mean just LD_PRELOAD libasan without linking against it?
Regarding less optimized libc, do you know if Ubuntu produces such versions for their packages?
Regards
________________________________
From: Florian Weimer <fweimer@redhat.com>
Sent: Wednesday, June 14, 2023 9:24 AM
To: Roger Phillips via Libc-help <libc-help@sourceware.org>
Cc: Roger Phillips <heidegg@hotmail.com>
Subject: Re: Getting more info about a heap corruption
* Roger Phillips via Libc-help:
> 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.
You could use LD_PRELOAD to install debugging malloc (such as the ASAN
allocator), or use LD_PRELOAD=libc.so.6 with a build of glibc (from the
same sources as the system glibc version) with reduced optimization.
I think there are also GDB scripts out there that traverse the various
heap data structures and report inconsistencies.
Thanks,
Florian
next prev parent reply other threads:[~2023-06-14 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 7:21 Roger Phillips
2023-06-14 9:24 ` Florian Weimer
2023-06-14 10:13 ` Roger Phillips [this message]
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=SJ0PR06MB8641391BD560EDBD3798022CAA5AA@SJ0PR06MB8641.namprd06.prod.outlook.com \
--to=heidegg@hotmail.com \
--cc=fweimer@redhat.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).