From: Dodji Seketeli <dodji@seketeli.org>
To: "Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org>
Subject: Re: [PATCH] ctf-reader: looks for debug information in out-of-tree modules
Date: Mon, 29 Aug 2022 13:02:37 +0200 [thread overview]
Message-ID: <87ler7l3ci.fsf@seketeli.org> (raw)
Message-ID: <20220829110237.MlgApN9JHMaPr4Qza4cZqioxzwUimStZsFxpxaGqDT8@z> (raw)
In-Reply-To: <20220815193209.3631681-1-guillermo.e.martinez@oracle.com> (Guillermo E. Martinez via Libabigail's message of "Mon, 15 Aug 2022 14:32:09 -0500")
Hello,
"Guillermo E. Martinez via Libabigail" <libabigail@sourceware.org> a
écrit:
> --
>
> The archive `vmlinux.ctfa' contain CTF debug information for
> all the types used by more than one module, CTF for the core
> kernel and CTF for each module compiled in Linux tree directory.
> CTF information for out-of-tree module is not present in
> `vmlinux.ctfa' file, even so, the compiler can emit the `.ctf'
> section into the out-of-tree modules and it can be extracted
> by the libabigail tools.
>
> * src/abg-ctf-reader.cc (process_ctf_archive, read_corpus
> slurp_elf_info): Avoid looks for `vmlinux.ctfa' when
> we aren't processing a `cur_corpus_group_'. So CTF
> info is embedded in the `.ko' file.
> * tests/data/Makefile.am: Add test inputs and expected files.
> * tests/data/test-read-ctf/test-linux-module.{ko,c,abi}: Add
> new test input and reference kABI.
> * tests/test-read-ctf.cc: Add new testcase.
>
> Signed-off-by: Guillermo E. Martinez <guillermo.e.martinez@oracle.com>
Applied to master, thanks!
[...]
Cheers,
--
Dodji
next prev parent reply other threads:[~2022-08-29 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 19:32 Guillermo E. Martinez
2022-08-29 11:02 ` Dodji Seketeli [this message]
2022-08-29 11:02 ` Dodji Seketeli
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=87ler7l3ci.fsf@seketeli.org \
--to=dodji@seketeli.org \
--cc=libabigail@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).