From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=c6dr=4R=gnu.org=eliz@sourceware.org>
Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10])
	by sourceware.org (Postfix) with ESMTPS id 66D803858D1E
	for <gdb-patches@sourceware.org>; Mon, 19 Dec 2022 12:48:08 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 66D803858D1E
Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gnu.org
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gnu.org
Received: from fencepost.gnu.org ([2001:470:142:3::e])
	by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.90_1)
	(envelope-from <eliz@gnu.org>)
	id 1p7FYs-0003kY-UD; Mon, 19 Dec 2022 07:48:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
	s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
	mime-version; bh=nBKEsV0eENSDJQ4ZpwemAbO+f+i3M61MnNWjbNPfups=; b=SbrbMbgEKI8V
	eOwkq5e7fWMH4AI6+VAdEpWjUlkFeC7/UBq/HTFWgdMpxfxPwTLY5c5TIawm3vgDWlqb0lOQy1T4L
	wETOOoDWSMBnaTtwFO2eGN8/aCh5etslMVhoX6/MlY1qwK27paqG2+Q00csezW2N8ss3AUJ/QEsGf
	ckGiV2fJvkle/MjfzkLgMPh9gOE/CXHS5NBI2hV3j7r/JfEmcBLrbgB5w3QkM+58YXWUyXiVILZmW
	3aPWuVJBQKAFieZ5txXF0t/d1xzIDV1dvshp6TfEZRuElBZmvhGqHRpEHudM7PTB2PTVOoN2uicTv
	iQKLflgdim/x2G3OLVxtfw==;
Received: from [87.69.77.57] (helo=home-c4e4a596f7)
	by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.90_1)
	(envelope-from <eliz@gnu.org>)
	id 1p7FYs-0004aG-FJ; Mon, 19 Dec 2022 07:48:06 -0500
Date: Mon, 19 Dec 2022 14:48:17 +0200
Message-Id: <83k02neezy.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Luis Machado <luis.machado@arm.com>
Cc: gdb-patches@sourceware.org
In-Reply-To: <58b64bf8-90b6-d080-c060-d03761501199@arm.com> (message from Luis
	Machado on Mon, 19 Dec 2022 10:07:27 +0000)
Subject: Re: Two observations using GDB 13 snapshot
References: <83h6xugc5v.fsf@gnu.org> <58b64bf8-90b6-d080-c060-d03761501199@arm.com>
X-Spam-Status: No, score=1.9 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_BARRACUDACENTRAL,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <gdb-patches.sourceware.org>

> Date: Mon, 19 Dec 2022 10:07:27 +0000
> From: Luis Machado <luis.machado@arm.com>
> 
> On 12/17/22 17:42, Eli Zaretskii via Gdb-patches wrote:
> > Using the latest snapshot of GDB 13 (MinGW build on native Windows), I
> > see some strange behavior I've not seen with previous versions:
> > 
> >    . Very long time to read symbols.  E.g., reading symbols of its own
> >      binary takes a whopping 2 minutes.  GDB 12.1 does the same in
> >      under 10 seconds.
> 
> There used to be a dwarf performance regression, but from looking at the bug (https://sourceware.org/bugzilla/show_bug.cgi?id=29105), it seems to be fixed.
> 
> I'm not sure if it manifests differently on MinGW.

This build is without std::thread.  Maybe it's related?

Does GDB 13 read DWARF debug info significantly differently than
previous versions?

Do you see this on GNU/Linux, when debugging GDB with itself, if you
disable multithreaded DWARF reading?

Thanks.