This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: GDB pretty-printers for glibc?
- From: Paul Smith <paul at mad-scientist dot net>
- To: Siddhesh Poyarekar <siddhesh dot poyarekar at gmail dot com>
- Cc: libc-help <libc-help at sourceware dot org>
- Date: Wed, 12 Jul 2017 15:59:23 -0400
- Subject: Re: GDB pretty-printers for glibc?
- Authentication-results: sourceware.org; auth=none
- References: <1499878516.25789.53.camel@mad-scientist.net> <CAAHN_R0E+Ax1vFt4d9ZgkOM_J=kRAAXwH9d=DAA4So9peeB8Zg@mail.gmail.com> <1499888932.25789.65.camel@mad-scientist.net> <CAAHN_R21M3+nPzo1=1SMwR+sG09-J5H7AmRA9AD6bsxknswLMA@mail.gmail.com>
- Reply-to: paul at mad-scientist dot net
On Thu, 2017-07-13 at 01:21 +0530, Siddhesh Poyarekar wrote:
> There isn't one, mainly because the file is tightly integrated with
> the structures in the glibc sources - it accesses internal structures
> that could change between releases.
Sure, I wasn't suggesting that it would be checked in or distributed
separately from the Git repo (although I will try filing a bug with
Debian requesting they add these pretty-printers to one of their glibc
dbg or dev packages).
But it seems like the conversion from the .pysym -> .py doesn't require
_compiling_ the entire glibc source tree... just configuring,
generating headers, etc., and compiling the output of the awk script
should be sufficient.
A special make target like "make py-const-files" or something could be
created that would do those steps without compiling all the C code.
At least based on my limited investigation.