From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gdb <gdb@sourceware.org>
Cc: Simon Marchi <simon.marchi@polymtl.ca>, doko@debian.org
Subject: Re: Considering removing CTF (Common Trace Format) support in GDB
Date: Thu, 07 Jan 2021 14:20:50 -0700 [thread overview]
Message-ID: <87a6tkv3yl.fsf@tromey.com> (raw)
In-Reply-To: <3fb1fbb6-836a-0e39-73a9-ef721630da88@polymtl.ca> (Simon Marchi via Gdb's message of "Mon, 4 Jan 2021 00:04:04 -0500")
>>>>> "Simon" == Simon Marchi via Gdb <gdb@sourceware.org> writes:
Simon> My personal opinion is (disclaimer: I work for EfficiOS, the company behind the
Simon> Babeltrace project): as much as I would like to see Babeltrace 2 being used
Simon> more, I don't think the CTF support in GDB, as it is today, makes sense.
...
Simon> So if CTF support doesn't help in sharing the data with other tools, then it
Simon> just becomes an alternative format to GDB's own format for saving/loading trace
Simon> data. And I don't think it's particularly useful to have two formats for this.
Sounds reasonable to me.
Tom
prev parent reply other threads:[~2021-01-07 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 5:04 Simon Marchi
2021-01-07 12:00 ` Luis Machado
2021-01-07 21:20 ` Tom Tromey [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=87a6tkv3yl.fsf@tromey.com \
--to=tom@tromey.com \
--cc=doko@debian.org \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).