From owner-soc-status@FreeBSD.ORG  Mon Jun 23 02:12:57 2014
Return-Path: <owner-soc-status@FreeBSD.ORG>
Delivered-To: soc-status@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 44F7A514
 for <soc-status@freebsd.org>; Mon, 23 Jun 2014 02:12:57 +0000 (UTC)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com
 [IPv6:2607:f8b0:4001:c03::22e])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 16F862FA7
 for <soc-status@freebsd.org>; Mon, 23 Jun 2014 02:12:57 +0000 (UTC)
Received: by mail-ie0-f174.google.com with SMTP id lx4so5342202iec.19
 for <soc-status@freebsd.org>; Sun, 22 Jun 2014 19:12:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=lLFnuhqPkYGst9wWyI3GlXnX4Gih5U7lMQtqc931FaM=;
 b=gwLv++q5cVJazui8U1ytGkI0r+0sABgGxxfdTEL21oaNbFHfWaBm7iezRUStqX1rIV
 mebrrtURp7KdF2L/jiSFTtK7hSC6gy6bp8lgIx2azjMkRc5wa+pDVViUs0L4pJ9EQEVu
 Ent6ZmriZGUP8fYC3KveTcrBiSojf20QHs7RAKpGzb1FvvHdyLc1H8JnTWgfLR0OlQZx
 EVoA++oAMtT2KEdXWH4xOTSzaFB7OOwhJnJh1u/zNmipGFKUWBTNhJb1evvTXxCbP5sG
 GSpA5tZb7xthAp4qlPEcJ5J4WOQBB2NahW51IohVwv4I/9elkeEj18HxARJaGwBKKVVw
 WVQA==
MIME-Version: 1.0
X-Received: by 10.43.77.205 with SMTP id zj13mr19991668icb.34.1403489576315;
 Sun, 22 Jun 2014 19:12:56 -0700 (PDT)
Received: by 10.64.103.226 with HTTP; Sun, 22 Jun 2014 19:12:56 -0700 (PDT)
Date: Mon, 23 Jun 2014 04:12:56 +0200
Message-ID: <CA+cSnN02=mSBjb5WMdxNHiWZfizVb=345cKrmVci8RL4JTgViQ@mail.gmail.com>
Subject: [libctf and DDB improvements] report #3 and #4
From: Daniel Lovasko <daniel.lovasko@gmail.com>
To: soc-status@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18
X-BeenThere: soc-status@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Summer of Code Status Reports and Discussion <soc-status.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/soc-status>,
 <mailto:soc-status-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/soc-status/>
List-Post: <mailto:soc-status@freebsd.org>
List-Help: <mailto:soc-status-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/soc-status>,
 <mailto:soc-status-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 02:12:57 -0000

Hello,

Right now this things are done:
 - reading of the whole CTF format (labels, types, ...)
 - parent reference solving
 - decompressing
 - public API to query the CTF data
 - error reporting from public API functions
 - ctfdump rewrite (still in beta stage)
 - everything seems to be working for the /boot/kernel/kernel file

The public API should not change very much, but the implementation may get
some polishing. I have done some basic performance and memory utilisation
tests and currently it takes ~0.2 seconds for the ctfdump to print all
information to a file (basic stdout redirection) and the maximal resident
set is ~20MB. Both tests were done with the kernel file /boot/kernel/kernel
(which is zipped).

Near future updates may include using valgrind to find some memleaks or
lint to check for potential bugs and to make the code more straight. Also,
the documentation seems to be few steps behind the code and algorithms, I
should fix that ASAP.

After that, I need to consult with George whether to continue with the
library to provide writing API or leave it for now and work on the DDB part
of the project.

The ctfdump code can be found here [1]
Any requests or questions are, of course, highly welcome.

Best,
Daniel

[1] https://github.com/lovasko/ctfdump