mailing list of musl libc
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: Srinivasan J <srinidpdk@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Dumping process heap from the core file
Date: Wed, 23 Jun 2021 14:32:24 -0400
Message-ID: <20210623183224.GO13220@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAEbeQ+pDRTG-FkTZmz2XEpkTe2yFps8WPWdF2Tj3uqeCzgNCqA@mail.gmail.com>

On Wed, Jun 23, 2021 at 09:21:49AM +0530, Srinivasan J wrote:
> Hi Rich,
>             Thank you for replying. Unfortunately, I need to debug a
> core which used musl-libc version v1.1.24 to get details about size of
> allocations in the heap. I see that mal.heap is no longer valid since
> 2015 [commit e3bc22f1eff87b8f029a6ab31f1a269d69e4b053].  So as you
> said the only way to walk the heap would be using a patched libc.so?
> Please do share any pointers.

Ah, in that case you could just start walking the headers
backward/forward from any known starting chunk.

Rich



> Reference:
> https://patchwork.criu.org/patch/10472/
> 
> Regards,
> Srini
> 
> On Sat, Jun 5, 2021 at 9:20 PM Rich Felker <dalias@libc.org> wrote:
> >
> > On Thu, Jun 03, 2021 at 07:39:54AM +0530, Srinivasan J wrote:
> > > Hi,
> > >     Is there an easy way to dump the heap from the process core which
> > > is using musl-libc? The process is using musl-libc version v1.1.24. I
> > > see that there is a _dump_heap() function, but that's not up to date.
> > > I am thinking about using _dump_heap() as reference. But any other
> > > suggestions are welcome.
> >
> > The mallocng heap structures are actually more walkable. There is
> > intentionally no public interface for doing this, but I have some
> > debug code left over from development that you could link into
> > static-linked programs with a particular known musl/mallocng version
> > or patch into libc.so for debugging purposes. I'll dig it up and post
> > it. Ping me if I forget about it.
> >
> > Rich

      reply	other threads:[~2021-06-23 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  2:09 Srinivasan J
2021-06-05 15:50 ` Rich Felker
2021-06-23  3:51   ` Srinivasan J
2021-06-23 18:32     ` Rich Felker [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=20210623183224.GO13220@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=srinidpdk@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

mailing list of musl libc

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.vuxu.org/musl

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 musl musl/ https://inbox.vuxu.org/musl \
		musl@inbox.vuxu.org
	public-inbox-index musl

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.musl


code repositories for the project(s) associated with this inbox:

	https://git.vuxu.org/mirror/musl/

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git