From: Dodji Seketeli <dodji@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Tyler Retzlaff <roretzla@linux.microsoft.com>,
Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org
Subject: Re: [PATCH] lib: add get/set link settings interface
Date: Fri, 05 Apr 2024 15:05:57 +0200 [thread overview]
Message-ID: <87h6ggklhm.fsf@redhat.com> (raw)
In-Reply-To: <CAJFAV8zV_5w4Z8rg8wRN9QxTxypVeTpdm04ym7iDBmE=A2vKCA@mail.gmail.com> (David Marchand's message of "Fri, 5 Apr 2024 10:58:57 +0200")
Hello,
> On Fri, Apr 5, 2024 at 2:55 AM Tyler Retzlaff
[...]
>> i'm jealous we don't have libabigail on windows, so helpful.
Heh, thank you for the kind words.
David Marchand <david.marchand@redhat.com> writes:
[...]
> libabigail is written in C++ and relies on the elfutils and libxml2
> libraries.
That is correct. Thank you for chiming in, David.
> I am unclear about what binary format is used in Windows... so I am
> not sure how much work would be required to have it on Windows.
So for a little bit of context, libabigail constructs its own internal
representation (IR) of the artifacts relevant to perform the analysis.
The middle-end of the system then performs the needed analysis on that
IR.
The binary format itself it handled by a front-end. Today, we have
front-ends that reads the ELF format and constructs the IR and hands it
over to the middle end.
One could very well imagine a new front-end that knows how to read the
Portable Executable (PE) format that is used on Windows, along with its
accompanying debug information.
Luckily, I've written articles[1][2] that explains how libabigail
recently switched to having a multi-front-end architecture that we have
used to support alternative debug information formats like CTF[3] and
BTF.
In light of that, adding a new PE front-end would be "just work to do",
I would think. And I would obviously not be opposed to helping such a
project and merging the result in the end.
As for any feature request, I would encourage potentially interested
parties to file an "enhancement request" on the bug tracker of the
project[4].
> That's more something to discuss with Dodji :-).
Thanks for the plug ;-)
I hope this helps.
[1]: https://developers.redhat.com/articles/2023/01/05/libabigail-multiple-debugging-formats#the_resulting_multi_front_end_architecture
[2]: https://www.redhat.com/en/blog/bpf-type-format-support-libabigail-23
[3]: https://lwn.net/Articles/795384/
[4]: https://sourceware.org/bugzilla/enter_bug.cgi?product=libabigail
Cheers,
--
Dodji
next prev parent reply other threads:[~2024-04-05 13:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 23:59 [PATCH] igc/ixgbe: " Marek Pazdan
2024-03-27 11:12 ` Bruce Richardson
2024-04-03 13:40 ` [PATCH] lib: " Marek Pazdan
2024-04-03 16:49 ` Tyler Retzlaff
2024-04-04 7:09 ` David Marchand
2024-04-05 0:55 ` Tyler Retzlaff
2024-04-05 0:56 ` Tyler Retzlaff
2024-04-05 8:58 ` David Marchand
2024-04-05 13:05 ` Dodji Seketeli [this message]
2024-04-03 13:59 ` Marek Pazdan
2024-04-03 14:48 ` Thomas Monjalon
2024-04-03 14:59 ` Marek Pazdan
2024-04-03 16:13 ` Thomas Monjalon
2024-04-03 17:23 ` Stephen Hemminger
2024-04-03 22:08 ` Marek Pazdan
2024-04-03 23:38 ` Stephen Hemminger
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=87h6ggklhm.fsf@redhat.com \
--to=dodji@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=thomas@monjalon.net \
/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 NNTP newsgroup(s).