From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20232 invoked by alias); 11 Oct 2015 08:57:21 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 20222 invoked by uid 89); 11 Oct 2015 08:57:20 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: smtp.gentoo.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Sun, 11 Oct 2015 08:57:18 +0000 Received: from vapier.lan (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with SMTP id 8072C340685; Sun, 11 Oct 2015 08:57:16 +0000 (UTC) Date: Sun, 11 Oct 2015 08:57:00 -0000 From: Mike Frysinger To: Pedro Alves , Ashutosh , Duane Ellis , Klaus Rudolph , gdb@sourceware.org Subject: Re: Using C++ code inside gdb Message-ID: <20151011085715.GE4119@vapier.lan> Mail-Followup-To: Pedro Alves , Ashutosh , Duane Ellis , Klaus Rudolph , gdb@sourceware.org References: <56178BAF.30904@redhat.com> <20151010213205.GB4119@vapier.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="n/aVsWSeQ4JHkrmm" Content-Disposition: inline In-Reply-To: <20151010213205.GB4119@vapier.lan> X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg00050.txt.bz2 --n/aVsWSeQ4JHkrmm Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1583 On 10 Oct 2015 17:32, Mike Frysinger wrote: > On 09 Oct 2015 10:41, Pedro Alves wrote: > > On 10/09/2015 07:08 AM, Ashutosh wrote: > > > Regarding using C++, I just hit upon the following conversation on the > > > gdb-patches list: > > > https://sourceware.org/ml/gdb-patches/2015-02/msg00202.html > > >=20 > > > where it seems that there's some work going on compiling gdb sources > > > with g++. Any idea if this support is available in some form already > > > in gdb 7.10 or when is it planned to be released? > >=20 > > The status in the wiki page linked from that url is accurate. > >=20 > > GDB nowadays builds and links in C++ when configured > > with --enable-build-with-cxx, though that still spews a ton of warnings. > > There's been constant incremental progress so we'll get there eventuall= y. > >=20 > > No release has been marked as the one where we'll switch to C++ as > > default language -- it'll get done when it's done; though the sooner > > the better. :-) >=20 > even if the C++ frontend is used, and C++ is the default language, that d= oesn't > mean that all C++ functionality will be accepted. there are a lot of des= ign > patterns and C++ APIs that are generally bad, and gdb is meant to be port= able. > so i'd expect there will be guidelines put together as to acceptable stan= dards > base (C11/C14/etc...) as well as headers and interfaces that are permitte= d and > ones that are banned. seems like gcc has already done this: https://gcc.gnu.org/codingconventions.html probably be best to try and follow that, or at least use it as a base. -mike --n/aVsWSeQ4JHkrmm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWGiRrAAoJEEFjO5/oN/WBIdsP/2fovge447kDor9kgxBZR+PO gpwu0QwaxntJtqNYQiAf1Bwfun9tbe/dGlm0maLNV9MeufScO3xwJ1Lii9aMTu+M 1pDq+KhBH6MPmfVUtPvarhv5mRbEH9KM1jMN879S/ERKsKwKbkdJ4gLd1xt6tNvn lSWic74quE21f7czaj54eT1d+Hhm/QitvTFdEgFHLWNxZRJx3aCSCGmTa7+uzbPA zYXqQnOcJXhAsjOvkce7i6Kw/4pBxPVaUfge312a1xOxsO2nkiFb6ZQgKiEVgdTX Byf0yW/bV345N6xJ2YLQ60WYYTuKqzoJK5gBSSOQkvClfmZQl5Uq45urJCN1RIK3 5aoFN1oQSclVVPHLH/o3T/n949SoWyu78E/fKpKmF1PCKSnFwQ3WQshrdsj5oQX2 mDb622FMDKlpftHiou3mlGyuVwvBdyDobMYMnvnGagOkY6KAONdFeF3g8lGDvXct qdQLH554/jcM9A2ReqSvV5Zy5IdjK59wLvyUP97Sv5JBDnu4Wtl/Kn/yNZgpWJtk tdTEhvRYG3TGKXrQwok2af4LKZGsDSDlUWNv/VXc3NBdURVtPho2jfFut4vkO5lk 7V6Df0n0GoAE9Jh+3rin06MmG60MUWU/xcAy2feyqNElKIYGg3moRjh1d5VQF3Sp 9/eDZu6B22+7emcLJND6 =LVST -----END PGP SIGNATURE----- --n/aVsWSeQ4JHkrmm--