From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, ARistovski@qnx.com, gbenson@redhat.com
Subject: Re: [PATCH v11 5/7] gdbserver build-id attribute generator
Date: Thu, 23 Jul 2015 17:24:00 -0000 [thread overview]
Message-ID: <831tfy4wiq.fsf@gnu.org> (raw)
In-Reply-To: <20150723172154.1176.3682.stgit@host1.jankratochvil.net>
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Aleksandar Ristovski <ARistovski@qnx.com>, Gary Benson <gbenson@redhat.com>
> Date: Thu, 23 Jul 2015 19:21:54 +0200
>
> Producer part of the new "build-id" XML attribute.
>
> gdb/ChangeLog
> 2015-07-15 Aleksandar Ristovski <aristovski@qnx.com
> Jan Kratochvil <jan.kratochvil@redhat.com>
>
> gdbserver build-id attribute generator.
> * features/library-list-svr4.dtd (library-list-svr4): New
> 'build-id' attribute.
>
> gdb/doc/ChangeLog
> 2015-07-15 Aleksandar Ristovski <aristovski@qnx.com
> Jan Kratochvil <jan.kratochvil@redhat.com>
>
> gdbserver build-id attribute generator.
> * gdb.texinfo (Library List Format for SVR4 Targets): Add
> 'build-id' in description, example, new attribute in dtd.
>
> gdb/gdbserver/ChangeLog
> 2015-07-15 Aleksandar Ristovski <aristovski@qnx.com
> Jan Kratochvil <jan.kratochvil@redhat.com>
>
> gdbserver build-id attribute generator.
> * linux-low.c (linux-maps.h, search.h, rsp-low.h): Include.
> (ElfXX_Ehdr, ElfXX_Phdr, ElfXX_Nhdr): New.
> (ELFXX_FLD, ELFXX_SIZEOF, ELFXX_ROUNDUP, BUILD_ID_INVALID): New.
> (find_phdr): New.
> (get_dynamic): Use find_pdhr to traverse program headers.
> (struct mapping_entry, mapping_entry_s, free_mapping_entry_vec)
> (compare_mapping_entry_range, struct find_memory_region_callback_data)
> (read_build_id, find_memory_region_callback, lrfind_mapping_entry)
> (get_hex_build_id): New.
> (linux_qxfer_libraries_svr4): Add optional build-id attribute
> to reply XML document.
The doco part is OK.
Thanks.
next prev parent reply other threads:[~2015-07-23 17:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 17:21 [PATCH v11 0/7] Validate binary before use Jan Kratochvil
2015-07-23 17:21 ` [PATCH v11 1/7] Create empty common/linux-maps.[ch] and common/target-utils.[ch] Jan Kratochvil
2015-07-23 17:21 ` [PATCH v11 2/7] Move gdb_regex* to common/ Jan Kratochvil
2015-07-23 17:21 ` [PATCH v11 3/7] Prepare linux_find_memory_regions_full & co. for move Jan Kratochvil
2015-07-23 17:22 ` [PATCH v11 5/7] gdbserver build-id attribute generator Jan Kratochvil
2015-07-23 17:24 ` Eli Zaretskii [this message]
2015-07-23 17:22 ` [PATCH v11 7/7] Tests for validate symbol file using build-id Jan Kratochvil
2015-07-23 17:22 ` [PATCH v11 6/7] Validate " Jan Kratochvil
2015-07-23 17:25 ` Eli Zaretskii
2015-07-23 17:22 ` [PATCH v11 4/7] Move linux_find_memory_regions_full & co Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831tfy4wiq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ARistovski@qnx.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox