From nobody Wed Feb 21 16:43:18 2024 X-Original-To: freebsd-toolchain@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Tg2CL1jQGz59vSJ for ; Wed, 21 Feb 2024 16:43:26 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tg2CK5z2zz4gK6 for ; Wed, 21 Feb 2024 16:43:25 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Authentication-Results: mx1.freebsd.org; none Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 00A763C019A; Wed, 21 Feb 2024 16:43:18 +0000 (UTC) Date: Wed, 21 Feb 2024 16:43:18 +0000 From: Brooks Davis To: Mark Millard Cc: FreeBSD Toolchain Subject: Re: system clang's -debugger-tuning setting: Is the default gdb setting intended? Message-ID: References: List-Id: Maintenance of FreeBSD s integrated toolchain List-Archive: https://lists.freebsd.org/archives/freebsd-toolchain List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4Tg2CK5z2zz4gK6 X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:199.48.128.0/22, country:US] On Tue, Feb 20, 2024 at 05:54:25PM -0800, Mark Millard wrote: > [Curiosity, not an objection.] > > It appears that most likely all FreeBSD platforms get the gdb > setting by default . . . I'm not sure we've thought about it much, but gdb is almost certainly the right default tuning since it's what most developers are accustom to. -- Brooks