mirror of
https://github.com/openharmony/third_party_elfutils.git
synced 2026-07-20 03:53:42 -04:00
6c8b68b024
Client objects now carry long-lived curl handles for outgoing connections. This makes it more efficient for multiple sequential queries, because the TCP connections and/or TLS state info are kept around awhile, avoiding O(100ms) setup latencies. debuginfod is adjusted to take advantage of this for federation. Other clients should gradually do this too, perhaps including elfutils itself (in the libdwfl->debuginfod_client hooks). A large gdb session with 117 debuginfo downloads was observed to run twice as fast (45s vs. 1m30s wall-clock time), just in nuking this extra setup latency. This was tested via a debuginfod intermediary: it should be even faster once gdb reuses its own debuginfod_client. Signed-off-by: Frank Ch. Eigler <fche@redhat.com>
The elfutils documentation is very much a work in progress. Contributions are welcome. Please reports bugs at https://sourceware.org/bugzilla/ Please send additions and patches to: elfutils-devel@sourceware.org The elfutils utilities are a new implementation of many of the utilities found in binutils and consequently, the documentation for most of the tools has been the the man pages for binutils. For example you could refer to readelf's man page for instructions on eu-readelf. This has been fine up until this point but as tools gain new capabilities, they will need to have their own individual man page. Forking the man pages from binutils is acceptable and the current plan of action. New utilities that do not have an analog in binutils can have their initial man pages generated using a tool like help2man. The C language interfaces for libelf, libdw, and libdwfl are in particular need of documentation. The aspirational goal is write these in sphinx.