From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTV BUG: Recent upgrades broke the JNI interface
Date: Sat, 11 Sep 2010 10:58:05 -0400 [thread overview]
Message-ID: <20100911145805.GC22938@Krystal> (raw)
In-Reply-To: <4C8A88FA.9090000@ericsson.com>
* Matthew Khouzam (matthew.khouzam at ericsson.com) wrote:
>
>
> On 10-09-08 05:47 PM, Mathieu Desnoyers wrote:
>> * Alexandre Montplaisir (alexandre.montplaisir at polymtl.ca) wrote:
>>
>>>
>>>>> You don't want a patch that makes the JNI functions access
>>>>> "marker_field->_offset", do you? I can carry it out-of-tree to restore
>>>>> the previous functionality (and compilability (is that a word?)) for
>>>>> TMF, until they change their parser methods, since they'll probably get
>>>>> hit by the same bug as LTTV.
>>>>>
>>>> Please don't do buggy workarounds at the library level to leave TMF
>>>> causy with its current bugs please. They must fix their app to upgrade
>>>> to the newer library version, period. I'm afraid we cannot release the
>>>> TMF package until they do.
>>>>
>>>> Thanks,
>>>>
>>>> Mathieu
>>>>
>>> "Your package is now uploading..."
>>> Ctrl-C, Ctrl-C...
>>>
>>> But still, don't you think a mostly working app with a "KNOWN BUGS:"
>>> disclaimer is better than a completely non-working one? I guess they can
>>> use an older version, which isn't much better.
>>>
>> Leave TMF with the old version until they adapt then.
>>
>> And common.. this is going to take a jiffy to fix. Why has this not been
>> done yet ? The new library has been out for a few weeks already.
>>
>
> The main reason is that no-one tested the latest and greatest version of
> libtraceread for the moment. We are currently working on narowing the
> gap with lttv on all versions of the library. That being said, a patch
> on TMF's side will be available soonish.
That's great, thanks !
Mathieu
>
> Matthew
>
>> Thanks,
>>
>> Mathieu
>>
>>
>>> Matthew: How long do you think it'd take to get fixed? It will require
>>> adjustments both in the jni_interface.c and the JniParser.java code in
>>> TMF, if I remember right.
>>>
>>> Cheers,
>>> Alexandre
>>>
>>>
>>>>> Cheers,
>>>>> Alexandre
>>>>>
>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Mathieu
>>>>>>
>>>>>>
>>>
>>
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2010-09-11 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 15:31 Alexandre Montplaisir
2010-09-08 15:47 ` Mathieu Desnoyers
2010-09-08 18:44 ` Alexandre Montplaisir
2010-09-08 21:09 ` Mathieu Desnoyers
2010-09-08 21:42 ` Alexandre Montplaisir
2010-09-08 21:47 ` Mathieu Desnoyers
2010-09-10 19:37 ` Matthew Khouzam
2010-09-11 14:58 ` Mathieu Desnoyers [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=20100911145805.GC22938@Krystal \
--to=compudj@krystal.dyndns.org \
/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