Re: dlmopen and core dumps

[Roland McGrath <roland at hack dot frob dot com>]

> In the case of in-process code that needs to do introspection,
> dl_iterate_phdr also misses the other namespaces, right?

Yes.  Which is to say, it always reports about the namespace containing
the caller of dl_iterate_phdr.

> If going the external-file route, I'd much rather glibc provided a
> declarative file, that describes where to find things, in a
> non-procedural way.  That could then be consumed by GDB in python, GDB
> native code, or whatever else wants to get at the info.

I'd like that too.  I was hoping for such a thing to be an option for the
pretty-printers too years ago now, before the Python method was chosen by
the GDB camp.  As there is today no such general declarative facility
available to drive GDB, complaining about some application or library not
using it is a non sequitur.  The options available today are GDB's Python
support and hard-coded knowledge of data structure layouts in GDB.