This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: RFC: api to walk memory allocations
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>, David Malcolm <dmalcolm at redhat dot com>, Tom Tromey <tromey at redhat dot com>, Rich Felker <dalias at aerifal dot cx>, David Ahern <dsahern at gmail dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 31 Oct 2013 13:35:09 -0700 (PDT)
- Subject: Re: RFC: api to walk memory allocations
- Authentication-results: sourceware.org; auth=none
- References: <527188A3 dot 4000305 at gmail dot com> <20131031004120 dot GF20515 at brightrain dot aerifal dot cx> <87fvri41cd dot fsf at fleche dot redhat dot com> <CAAHN_R0QvQ5H-Si5pAYAYp6sK9yzu94xsC4hn6pGga-UGdqXtg at mail dot gmail dot com> <87wqkt325r dot fsf at fleche dot redhat dot com> <1383232710 dot 5282 dot 9 dot camel at surprise> <CAAHN_R28bMLpGrqNBpTgv6PT2tjN-q=bsmZuwdfYg42MYQHHZQ at mail dot gmail dot com> <5272B48B dot 2050002 at redhat dot com>
Before the existing work was pointed out, I was going to suggest to the
original requester that we start with a gdb-python module for on-demand
debugger investigation (which you can do not-too-invasively with a quick
attach+dump+detach gdb script) and consider the subject further only after
real-world experience trying to address the real-world cases with this
approach and producing convincing evidence that it is insufficient (of
which I am skeptical).