From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by server2.sourceware.org (Postfix, from userid 48) id B0A70385F024; Sun, 8 Mar 2020 13:14:01 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 server2.sourceware.org B0A70385F024 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1583673663; bh=phMlxeJ1o3mGQqA97iIFpm1yAPSIx7tDFCOubkLjwxc=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Txf7Feezg04UN8LqUzI30E6PNmbsMU+UHq/AX3WNzShpohS2BZ/XxAfSi/+aD9h8g lOVpF1TeZueLovgSvBPgMR+kx6zvbI9Zmj+gf92kJ98QJeFSRC8UGFYKUNOGtd8Fgm xuF7z0iuae9uuMRq8QVp5Mk5vIGEbTH8FOddxNYQ= From: "jan.kratochvil at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/23710] gdb is slow and memory hungry consuming debug generated with LTO by GCC Date: Sun, 08 Mar 2020 13:14:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 8.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jan.kratochvil at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Spam-Status: No, score=-7.9 required=5.0 tests=ALL_TRUSTED, BAYES_00, GIT_PATCH_2 autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Mar 2020 13:21:03 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D23710 --- Comment #12 from Jan Kratochvil --- (In reply to Tom de Vries from comment #11) > $ time.sh lldb -batch cc1.dwz -o "b do_rpo_vn" FYI upstream LLDB does not yet support DWZ to make such measurement valid. There is an off-trunk patchset for it: git clone -b dwz git://git.jankratochvil.net/lldb It works but it is still being refactored to get it accepted upstream. --=20 You are receiving this mail because: You are on the CC list for the bug.=