public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Roger Phillips <heidegg@hotmail.com>
Cc: Roger Phillips via Libc-help <libc-help@sourceware.org>
Subject: Re: Getting more info about a heap corruption
Date: Wed, 14 Jun 2023 12:17:14 +0200	[thread overview]
Message-ID: <87o7liqrf9.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <SJ0PR06MB8641391BD560EDBD3798022CAA5AA@SJ0PR06MB8641.namprd06.prod.outlook.com> (Roger Phillips's message of "Wed, 14 Jun 2023 10:13:12 +0000")

* Roger Phillips:

> Thanks for the answer! Do you mean just LD_PRELOAD libasan without
> linking against it?

Yes, I think this will work in at least some cases.  There are other
debugging memory allocators that could be used in a similar way, of
course.

> Regarding less optimized libc, do you know if Ubuntu produces such
> versions for their packages?

I don't think so.  You'd have to rebuild glibc yourself with different
build flags, using their build process, but you don't have to install
the result.  Just copy the libc-2.31.so file and LD_PRELOAD it on the
target system.  Note that you need to rebuild the exact same glibc
version, otherwise it might not work.  And you have to do the rebuild
for each libc6 package update.

Thanks,
Florian


  reply	other threads:[~2023-06-14 10:17 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
2023-06-14 10:17     ` Florian Weimer [this message]
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=87o7liqrf9.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=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).