public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "xdegaye at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/14903] New: incorrect handling of unicode filenames by gdb-mi Date: Sat, 01 Dec 2012 13:17:00 -0000 [thread overview] Message-ID: <bug-14903-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14903 Bug #: 14903 Summary: incorrect handling of unicode filenames by gdb-mi Product: gdb Version: 7.3 Status: NEW Severity: normal Priority: P2 Component: mi AssignedTo: unassigned@sourceware.org ReportedBy: xdegaye@gmail.com Classification: Unclassified The following session shows that although gdb correctly prints the filename 'π' as the valid unicode sequence b'\xcf\x80', gdb-mi prints an invalid unicode byte sequence: b'\xcf\x5c' followed by '200'. $ ls -l total 0 -rw-r--r-- 1 xavier xavier 0 2012-12-01 13:07 π $ cat ../complete_file.txt complete file $ gdb -batch -nx -x ../complete_file.txt | od 0000000 656c6966 0a80cf20 >file ...< 0000008 $ gdb --interpreter=mi -batch -nx -x ../complete_file.txt | od 0000000 7268743d 2d646165 756f7267 64612d70 >=thread-group-ad< 0000016 2c646564 223d6469 0a223169 6966227e >ded,id="i1".~"fi< 0000032 cf20656c 3030325c 0a226e5c >le .\200\n".< 0000044 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-12-01 13:17 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-01 13:17 xdegaye at gmail dot com [this message] 2021-06-19 14:39 ` [Bug mi/14903] " a27573 at outlook 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-14903-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: 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).