Re: [PATCH 2/4] python support for fetching separate debug files: have_debug_info

[Doug Evans <dje@google.com>]

On Fri, Nov 21, 2014 at 12:22 PM, Doug Evans <dje@google.com> wrote:
> Another way we *could* go, which I kinda like, is to provide a general
> purpose ELF API to Python, or try to do the bfd kind of thing and
> abstract away ELF vs COFF, etc, and export that through gdb.  Then one
> could determine if debug info is present that way. If I were to do the
> former (the ELF API) I'd like to make it separate from gdb: why write
> something only some users can use.  The latter (abstract away the file
> format) has its own problems of course, but one might simplify it to
> something along the lines of what libiberty/simple-object* provides.
> Either of these solutions allows one to watch for a special section
> pointing at separate debug info (e.g., .gnu_debuglink).
>
> [Down the road exporting a DWARF reader to Python would be useful too,
> but that's later.  If it involved providing our own libelf/libdwarf so
> much the better.]

Filing for reference sake.
Another way to go, which I partially implemented,
was to export bfd's iovec to Python.
In the end it was more complex than I needed.