From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7CA963857C52; Fri, 15 Mar 2024 13:04:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7CA963857C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1710507864; bh=N0STlSaQywT4SVpfSOhTL3p888YWE/o5P6vLm908cwA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Ar7s7GCHQyUy6s+ISiqCSSjCHgXOnibUS+tgiVryY1s2JkGpEidJrGqj+m2SgTGBP m3xaVMevvQRUVbm6syVsM28I7y3yQUFvrBJFeb+UepDXU+bxZw1ryv9owC/RsuybRm nmDkjxhzOFrolLjyeuGNJCFIldiKeCBzxP/y8yT0= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/16420] Gdb cannot print static variables when code is compiled but not linked with -flto Date: Fri, 15 Mar 2024 13:04:23 +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: 7.6 X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: OBSOLETE X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution cc 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D16420 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |OBSOLETE CC| |tromey at sourceware dot o= rg --- Comment #2 from Tom Tromey --- (In reply to Hannes Domani from comment #1) > Sounds to me more like a problem on gcc side. > And I can't reproduce it. Given its age & lack of reproducibility, let's close it. Branko -- if this is still an issue for you, please comment and/or reopen the bug, I guess maybe with a reproducer. Often though this sort of thing turns out to be a compiler problem, where gdb is just doing what the compiler tells it. --=20 You are receiving this mail because: You are on the CC list for the bug.=