public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/16020] New: Print trailing nul in c++ std::string?
Date: Tue, 08 Oct 2013 22:04:00 -0000	[thread overview]
Message-ID: <bug-16020-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 16020
           Summary: Print trailing nul in c++ std::string?
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com

Feel free to move this to libstdc++ if warranted, but most of the
pretty-printing of std strings is in gdb so I figured I'd start here.
[Whether printing of lazy strings correctly falls under category python or c++
or whatever ... feel free to correct that too.]

Consider:

#include <string>
#include <iostream>

using namespace std;

int
main (void)
{
  static const char foo[] = "abc";
  string foo0_str (foo, sizeof (foo));
  string foo_str (foo, sizeof (foo) - 1);

  cout << "foo0_str: \"" << foo0_str << "\"\n";
  cout << "foo_str: \"" << foo_str << "\"\n";

  return 0;
}

Here is the output:

$ ./trailing-nul.x64
foo0_str: "abc^@"
foo_str: "abc"

However, the trailing nul in foo0_str is not included in pretty-printed output:

(gdb) p foo0_str
$1 = "abc"
(gdb) p foo_str
$2 = "abc"

Bug?

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


             reply	other threads:[~2013-10-08 22:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 22:04 dje at google dot com [this message]
2013-10-08 22:21 ` [Bug python/16020] " b.r.longbons at gmail dot com

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-16020-4717@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).