public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.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	[thread overview]
Message-ID: <bug-16420-4717-FBllE9b5sj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16420-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16420

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |OBSOLETE
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
(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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2024-03-15 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 11:23 [Bug gdb/16420] New: " branko.drevensek at gmail dot com
2024-01-02 12:02 ` [Bug gdb/16420] " ssbssa at sourceware dot org
2024-03-15  9:31 ` sam at gentoo dot org
2024-03-15 13:04 ` tromey at sourceware dot org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-16420-4717-FBllE9b5sj@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).