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/18436] Can't print dynamically allocated global array
Date: Thu, 03 Aug 2023 15:53:49 +0000	[thread overview]
Message-ID: <bug-18436-4717-JcjVGAB2SR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18436-4717@http.sourceware.org/bugzilla/>

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

Tom Tromey <tromey at sourceware dot org> changed:

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

--- Comment #11 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to stanton from comment #10)
> Final follow-up (for now):
> 
> gdb works fine if you add a -g flag to both the compilation and the linking
> step. Not sure why, but at least it’s working now.

I don't know why either, normally -g isn't needed at link time.
Anyway, I'm going to close this, since it seems to work.

If you think that's in error, we can reopen it.
One potential issue here is that the macOS port isn't really maintained.

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

      parent reply	other threads:[~2023-08-03 15:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  4:54 [Bug gdb/18436] New: " stanton at haas dot berkeley.edu
2015-05-20 16:34 ` [Bug gdb/18436] " keiths at redhat dot com
2015-05-20 17:15 ` stanton at haas dot berkeley.edu
2015-05-20 17:48 ` keiths at redhat dot com
2015-05-20 18:13 ` stanton at haas dot berkeley.edu
2015-05-21 17:26 ` stanton at haas dot berkeley.edu
2023-08-03 15:53 ` 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-18436-4717-JcjVGAB2SR@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).