From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by server2.sourceware.org (Postfix, from userid 48) id 9BC9C385E82C; Sun, 8 Mar 2020 11:10:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 server2.sourceware.org 9BC9C385E82C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1583666107; bh=EPqWFUq6SJ8gvfmFj6wxmUAz/JGjmlDsRm05ylebXcE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KWF1GH4c8jOjBIgi7Hk9W2Xo9G76k7Vi2e78IQYNcpqKO2iCkCcRaaS/gGciX0Vf+ +E9tN9RK/M8Ln86cViF5t2q8lF+KpbQjZvfDUIZsEuhF2RY6kqwjaIRI49qcCH36gV 6rIlhR6eN6605k2Ryftu1nFhRBGh2eup0wIfR1mw= From: "vries at gcc dot gnu.org" 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 11:09:59 +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: vries at gcc dot gnu.org 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 11:15:07 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D23710 --- Comment #11 from Tom de Vries --- Comparison, cc1 vs cc1.dwz (produced using dwz build from current master branch): ... $ diff.sh cc1 cc1.dwz .debug_info red: 49.30% 97418416 49399513 .debug_abbrev red: 42.04% 1699940 985372 .debug_str red: 0% 6344030 6344030 total red: 46.21% 105462386 56728915 ... lldb roughly uses same amount of memory, that is: cc1.dwz uses 5.7% less: ... $ time.sh lldb -batch cc1 -o "b do_rpo_vn" (lldb) target create "cc1" Current executable set to 'cc1' (x86_64). (lldb) b do_rpo_vn Breakpoint 1: 3 locations. maxmem: 519116 real: 2.63 user: 4.21 system: 0.14 $ time.sh lldb -batch cc1.dwz -o "b do_rpo_vn" (lldb) target create "cc1.dwz" Current executable set to 'cc1.dwz' (x86_64). (lldb) b do_rpo_vn Breakpoint 1: 3 locations. maxmem: 489596 real: 2.78 user: 4.01 system: 0.10 ... With gdb, the difference is a reduction of 51.9%: ... $ time.sh gdb cc1 -batch -iex "set language c++" -iex "maint set dwarf max-cache-age 316" -ex "b do_rpo_vn" Breakpoint 1 at 0xd40e30: do_rpo_vn. (2 locations) maxmem: 999404 real: 7.03 user: 6.81 system: 0.25 $ time.sh gdb cc1.dwz -batch -iex "set language c++" -iex "maint set dwarf max-cache-age 316" -ex "b do_rpo_vn" Breakpoint 1 at 0xd40e30: do_rpo_vn. (2 locations) maxmem: 481152 real: 6.15 user: 6.09 system: 0.12 ... --=20 You are receiving this mail because: You are on the CC list for the bug.=