From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 70602 invoked by alias); 10 Oct 2015 21:32:10 -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 70591 invoked by uid 89); 10 Oct 2015 21:32:09 -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; Sat, 10 Oct 2015 21:32:08 +0000 Received: from vapier.lan (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with SMTP id 35E77340662; Sat, 10 Oct 2015 21:32:06 +0000 (UTC) Date: Sat, 10 Oct 2015 21:32:00 -0000 From: Mike Frysinger To: Pedro Alves Cc: Ashutosh , Duane Ellis , Klaus Rudolph , gdb@sourceware.org Subject: Re: Using C++ code inside gdb Message-ID: <20151010213205.GB4119@vapier.lan> Mail-Followup-To: Pedro Alves , Ashutosh , Duane Ellis , Klaus Rudolph , gdb@sourceware.org References: <56178BAF.30904@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <56178BAF.30904@redhat.com> X-IsSubscribed: yes X-SW-Source: 2015-10/txt/msg00049.txt.bz2 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1370 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 eventually. >=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. :-) even if the C++ frontend is used, and C++ is the default language, that doe= sn't mean that all C++ functionality will be accepted. there are a lot of design patterns and C++ APIs that are generally bad, and gdb is meant to be portab= le. so i'd expect there will be guidelines put together as to acceptable standa= rds base (C11/C14/etc...) as well as headers and interfaces that are permitted = and ones that are banned. saying "it's C++ now!" is pretty vague ;). -mike --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIbBAEBCAAGBQJWGYPRAAoJEEFjO5/oN/WBSgsP+Mvqkja68QgMMZUEpPSMaYUh P2Q3Fz+y6ixARddTZEkPKWCq4c0wRt85hCtcp+NEWvcdp42vx23eHrdPM6XaK+LA glqFTJzAlbq27vQrMsEhTF/gY8+voHezx+vC8RDk/7S66OHcSpXXr4nYZJUnf3QT 61i/1bNJkmu247at62WtcskDmV1D/K7BchmD5d8Kckd+Ti8XO/5EihIwMSN409UQ CDOpxEeHayTRtx0JBfY6TvabgH8Mo2NH0xbmS+xevxYdVtuMnY9SlaVBPOi8KRu4 qwDNQc3/1NUshrHFYB2DSjLp2gZMGp/9CQMeD3d1diOSt69pGjblto/rs+XFrX0h LfX0geyLnmzRdJqtUoLf3bF6T+urBvWD3QKpLtJhmI1jJKqF47GNqAQT30kt65+f i79aruYeMqCwIILR8h8B26ASgrOiIkmilLNK9yT9ZST0wSdrE8rj+d4rtz6kakoZ 1FR0DRiPFgMqIQwXU/zNBFTi2IBzigVxZWsmVTUUiWiNI7wPIY2icJH4U91Da7QO d915yeKxrJeCg9jgMPLPQEQqunnr9EkMOO1vW43eavKyX01FoWkP92iTgVYcJxWl G9QLtTqnHK5cwXHFaX8yn40hks3D8jgPMzzHACPtcM/FKAPEtsG9KPMHrTrHcJtb sClUx/hP+d38S2Qggw4= =F3yu -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--