From: Phil Muldoon <pmuldoon@redhat.com>
To: Petr Machata <pmachata@redhat.com>
Cc: Sami Wagiaalla <swagiaal@redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
frysk <frysk@sourceware.org>
Subject: Re: elfutils use patterns in frysk
Date: Tue, 06 Nov 2007 21:56:00 -0000 [thread overview]
Message-ID: <4730E2F0.3030204@redhat.com> (raw)
In-Reply-To: <4730DE37.8070703@redhat.com>
Petr Machata wrote:
> I don't really deal with corefiles. I've written what I needed for
> fl?trace, which was handling of symbols and their versions, and few
> related things. Those are usually very straightforward libelf wrappers.
>
>
Sorry, not in respect to corefiles, but what you have written for symbol
usage. I think general solicitation as to how Frysk uses elfutils would
build a bigger picture so that the C++ bindings Frank is working on
could be properly targeted?
Regards
Phil
>> Phil
>>
>
> PM
>
>
prev parent reply other threads:[~2007-11-06 21:56 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
2007-11-06 21:36 ` Petr Machata
2007-11-06 21:56 ` Phil Muldoon [this message]
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=4730E2F0.3030204@redhat.com \
--to=pmuldoon@redhat.com \
--cc=fche@redhat.com \
--cc=frysk@sourceware.org \
--cc=pmachata@redhat.com \
--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).