From: David.OShea@quantum.com (David OShea)
Subject: [lttng-dev] babletrace with python bindings
Date: Mon, 7 Jan 2013 04:40:03 +0000 [thread overview]
Message-ID: <20998D40D9A2B7499CA5A3A2666CB1EB19F8ABF4@ZURMSG1.QUANTUM.com> (raw)
In-Reply-To: <20121219183932.GA9587@Krystal>
> -----Original Message-----
> From: Mathieu Desnoyers [mailto:mathieu.desnoyers@efficios.com]
> Sent: Thursday, 20 December 2012 5:10 AM
> To: ajonwa ajonwa
> Cc: lttng-dev at lists.lttng.org
> Subject: Re: [lttng-dev] babletrace with python bindings
>
> * ajonwa ajonwa (ajonwa at gmx.com) wrote:
> > Hello everyone,
> >
> > I get the following error message while attempting to compile
> babeltrace with python bindings:
[...]
> This branch is currently in development, and might be out of sync with
> the master branch of babeltrace at the moment. We don't have immediate
> plans to work on it, but bontributions are welcome.
Apologies for the late reply. I just wanted to point out that if you check out commit 24a3136a383, it does build. It's an older version of babeltrace, but does work despite some bugs.
The main bug I recall is that iterator.set_pos(babeltrace.IterPos(babeltrace.SEEK_BEGIN)) doesn't fail immediately, and works in some traces, but sometimes results in a subsequent assertion failure in the Python interpreter after a few events have been read, or returns a bogus event at the start of the trace. Quite possibly this is a babeltrace bug that has been fixed already.
Regards,
David
----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.
next parent reply other threads:[~2013-01-07 4:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121218184045.288000@gmx.com>
[not found] ` <20121219183932.GA9587@Krystal>
2013-01-07 4:40 ` David OShea [this message]
2013-01-13 17:54 ` Mathieu Desnoyers
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=20998D40D9A2B7499CA5A3A2666CB1EB19F8ABF4@ZURMSG1.QUANTUM.com \
--to=david.oshea@quantum.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