public inbox for
 help / color / mirror / Atom feed
From: Petr Machata <>
Subject: ftrace status
Date: Sun, 06 Apr 2008 07:37:00 -0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

I've just pushed huge pile of patches that constitute rewrite of ftrace
so that it uses already present frysk infrastructure, namely breakpoint
manager and breakpoint classes, instead of inventing its own services.
Current status is close to what ftrace used to be capable of doing. Some
things are still not there, but I have non-frysk dues in plan for next
week or two, and don't want to sit on the patchset for uncertain number
of weeks without further progress.

What doesn't work anymore: symbol aliases and ELF symbol versioning are
not handled.  There is at least one mysterious bug that causes something
deep in frysk to place breakpoints to bogus addresses, I haven't had a
time to properly debug it yet.  x86_64 has not seen a single test run,
so chances are ftrace will just collapse there.

On the upside, ftrace now speaks debuginfo, which it didn't used to; and
there are couple new interfaces in Frysk framework, that allow e.g. ELF
symbol table loading or PLT entry computations.  Although cleanups are
due in places.

I've taken the opportunity and changed several commandline arguments
while doing the overall revamp.  Manual page has been updated to reflect

Have fun,

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2008-04-06  7:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06  7:37 Petr Machata [this message]
2008-04-07 15:24 ` Petr Machata

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).