public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "msharov at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/31118] Error printing vectors when using nonstandard stdlib
Date: Thu, 07 Dec 2023 13:43:42 +0000	[thread overview]
Message-ID: <bug-31118-4717-RpZQWtFOvr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31118-4717@http.sourceware.org/bugzilla/>

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

Mike Sharov <msharov at users dot sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |NOTABUG

--- Comment #2 from Mike Sharov <msharov at users dot sourceforge.net> ---
(In reply to Simon Marchi from comment #1)
> If you are getting this message, it means the pretty printer for gcc's
> stdlib has been loaded.  How come, since you don't use gcc's stdlib?

I have tried to reproduce with a simpler test case and discovered that one of
the libraries my app was linked to was dynamically loading libstdc++. So gdb
behavior here is not unreasonable after all. I guess that means you can close
the bug.

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

      parent reply	other threads:[~2023-12-07 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 22:09 [Bug c++/31118] New: " msharov at users dot sourceforge.net
2023-12-07  2:24 ` [Bug c++/31118] " simon.marchi at polymtl dot ca
2023-12-07 13:43 ` msharov at users dot sourceforge.net [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-31118-4717-RpZQWtFOvr@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).