From: Phil Muldoon <pmuldoon@redhat.com>
To: Sami Wagiaalla <swagiaal@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, frysk <frysk@sourceware.org>
Subject: Re: elfutils use patterns in frysk
Date: Tue, 06 Nov 2007 18:25:00 -0000 [thread overview]
Message-ID: <4730B19C.9080207@redhat.com> (raw)
In-Reply-To: <4730A923.4080100@redhat.com>
Sami Wagiaalla wrote:
> Hi Frank,
>
> A while back you asked about elfutils use patterns in Frysk.
> I only know abut libdw* so everybody feel free to add to this:
FWIW I believe the current code that is in the frysk-sys/lib/dwfl is
based on a simple facade OOP pattern (as far as I can tell, I was not
the original author of this code). So imo it should be noted that what
we have are not, and should never be considered as a binding. For
example there is no memory management, and there is a simple
transactional contract that does not exist outside of each call.
>
> Okay so there are two types of items here:
A third usage pattern is elf bindings for building corefiles, which are
not dwfl based. These are fundamental bindings (ElfSection, ElfEHeader,
ElfSectionHeader, ElfProgramHeader, ElfData) and so on.These are
basically 1:1 mappings on the Gelf api. There is also some meta-code
that deals with corefile note based bindings, but these are likely to be
very specialized. I do not consider these as a first priority (or a
second, or third) for Frank's work. I can't think who would use them
other than Frysk and we already have custom code that deals with that.
I know Petr uses these in some way as well. Maybe he can add more detail
here.
Regards
Phil
next prev parent reply other threads:[~2007-11-06 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 17:49 Sami Wagiaalla
2007-11-06 18:25 ` Phil Muldoon [this message]
2007-11-06 21:36 ` Petr Machata
2007-11-06 21:56 ` Phil Muldoon
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=4730B19C.9080207@redhat.com \
--to=pmuldoon@redhat.com \
--cc=fche@redhat.com \
--cc=frysk@sourceware.org \
--cc=swagiaal@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).