From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: fwd: is LLDB a threat to GDB's success? #999
Date: Fri, 13 Feb 2015 12:35:00 -0000 [thread overview]
Message-ID: <54DDEF90.4090209@redhat.com> (raw)
In-Reply-To: <20150213110919.GN5709@adacore.com>
I should perhaps add that the opinion expressed was mine alone
and does not represent the opinions of my past, present, and
future employer(s). :-)
Pedro alves wrote:
>> - Good C++ support.
>>
>> This stems from modularity. lldb reuses llvm/clang (the C/C++ compiler
>> frontend) for expression evaluation/parsing, thus it has excellent
>> C++ support. GDB has its own built in C++ expression parser, which
>> is poor. GNU of course already has excellent parsers inside GCC/G++,
>> but unfortunately, for years GCC did not really welcome modularity
>> and reuse, and that now bites back, hard. As the C++ world shifts
>> more and more to C++11/C++14, the more GDB is bitten by this,
>> as it doesn't understand basic new features that have been added
>> to the language. LLDB gains support for such new features for
>> free whenever clang gains support for the same.
This of course was missing lots of context, but, I'll add that
GDB's not actually sitting and waiting here. There's a project
going on already that is exactly about reusing GCC/G++ in GDB.
The first step has landed in GDB 7.9 already, in the form of
the "compile" command, which compiles, injects, and executes
a C expression, making use of GCC through a plugin. See:
https://sourceware.org/gdb/current/onlinedocs/gdb/Compiling-and-Injecting-Code.html
We're discussing next steps for the project here:
https://sourceware.org/ml/gdb/2015-02/msg00019.html
Everyone's more than welcome to join!
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-02-13 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 11:09 Joel Brobecker
2015-02-13 12:35 ` Pedro Alves [this message]
2015-02-13 15:51 ` Shahbaz Youssefi
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=54DDEF90.4090209@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.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