Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Gige Atanasoaie <Gige.Atanasoaie@bc-s.com>,
	"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [babeltrace2] Integration with Wireshark
Date: Mon, 9 Dec 2024 15:44:57 -0500	[thread overview]
Message-ID: <7338127c-5f0f-4bcb-aeb9-ed29459e2424@efficios.com> (raw)
In-Reply-To: <KL1PR0601MB3987E8EC377E357825D82546C2312@KL1PR0601MB3987.apcprd06.prod.outlook.com>

Hi Gige,

On 12/6/24 1:48 AM, Gige Atanasoaie via lttng-dev wrote:
> Hi,
> 
> First, I’d like to thank you for the CTF, barectf and babeltrace2 projects.
> 

On behalf of the contributors, thanks :)

> We’d like to use CTF in one of our projects (traces generated by barectf and lttng).
> 
> Wondering if someone tried to integrate libbabeltrace2 in Wireshark plugins (wiretap, epan), to get the CTF traces decoded together with other packet types by Wireshark.
> Is any project of this type known by community?
> 

I'm not aware of any project that does this.

In the use-case you imagine, are you thinking of using Wireshark to 
analyze network packets that contain trace data (e.g., from lttng-live), 
or are you thinking more about opening a whole CTF trace with Wireshark?

thanks,
kienan

> Thank you and best regards,
> Gige
> 
> Confidentiality: This e-mail and any attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose, or store or copy the information in any medium.


      reply	other threads:[~2024-12-09 20:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06  6:48 Gige Atanasoaie via lttng-dev
2024-12-09 20:44 ` Kienan Stewart via lttng-dev [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=7338127c-5f0f-4bcb-aeb9-ed29459e2424@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=Gige.Atanasoaie@bc-s.com \
    --cc=kstewart@efficios.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