From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CD3F9385AC3C; Thu, 7 Dec 2023 13:43:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CD3F9385AC3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1701956622; bh=DLNgeNzoQBoNbrsYkMwTkmVjD4n5/wH4UHG3y4AVLO8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=s2eS7P7PY4VyPUeJZXLPNN6ROnfRSzMjh41vjnb3ovLexoOPayHRK+1UCQ/WdhAgZ tQ6iroXIt+chyDkFT301jUD+sVU2S6NGDYPkJ1RVlJdlNmtQNhdpe7zAM687amE1kj 9wCDK6NqIU9ec71pVF6tM/Q5oTX28ii52O0+1qnw= From: "msharov at users dot sourceforge.net" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: msharov at users dot sourceforge.net X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: NOTABUG 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 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=3D31118 Mike Sharov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #2 from Mike Sharov --- (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 clo= se the bug. --=20 You are receiving this mail because: You are on the CC list for the bug.=