public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "sourceware.org at tropp dot de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16501] std::wstring and std::vector are shown with wrong information when debugging a constructor Date: Thu, 23 Jan 2014 10:08:00 -0000 [thread overview] Message-ID: <bug-16501-4717-tDYfyNaGFA@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16501-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16501 --- Comment #1 from utro <sourceware.org at tropp dot de> --- Created attachment 7370 --> https://sourceware.org/bugzilla/attachment.cgi?id=7370&action=edit example c++ header file -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-23 10:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-23 10:07 [Bug gdb/16501] New: " sourceware.org at tropp dot de 2014-01-23 10:08 ` sourceware.org at tropp dot de [this message] 2014-01-23 10:37 ` [Bug gdb/16501] " sourceware.org at tropp dot de 2024-01-01 23:09 ` ssbssa at sourceware dot org
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-16501-4717-tDYfyNaGFA@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: linkBe 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).