public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mariano.bessone at tallertechnologies dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/61835] New: Invalid comment on pretty printers breaks gdb Date: Thu, 17 Jul 2014 19:47:00 -0000 [thread overview] Message-ID: <bug-61835-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61835 Bug ID: 61835 Summary: Invalid comment on pretty printers breaks gdb Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: mariano.bessone at tallertechnologies dot com Created attachment 33136 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33136&action=edit Workaround Running gdb with latest pretty printers causes: Traceback (most recent call last): File "<string>", line 3, in <module> File "/data/utils/prettyprinters/libstdcxx/v6/printers.py", line 1056 """ SyntaxError: (unicode error) 'unicodeescape' codec can't decode bytes in position 194-195: malformed \N character escape /home/marjobe/.gdbinit:6: Error in sourced command file: Error while executing Python code. The problem is that a comment contains an escape sequence. See workaround in the attached patch.
next reply other threads:[~2014-07-17 19:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-17 19:47 mariano.bessone at tallertechnologies dot com [this message] 2014-07-18 15:56 ` [Bug libstdc++/61835] " redi at gcc dot gnu.org 2014-07-18 15:58 ` redi at gcc dot gnu.org 2014-07-18 18:37 ` mariano.bessone at tallertechnologies 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-61835-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).