public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug c++/10908] error reading variable for char variable Date: Tue, 21 Dec 2010 18:26:00 -0000 [thread overview] Message-ID: <bug-10908-4717-u1EykA90fZ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-10908-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=10908 Tom Tromey <tromey at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Target Milestone|7.1 |7.3 --- Comment #7 from Tom Tromey <tromey at redhat dot com> 2010-12-21 15:26:00 UTC --- I put in a fix a while back that disables the use of iconv on many systems, including Solaris. The change will appear in gdb 7.3. One thing that would be useful in the future is to know how to write a test to see whether a newer Solaris has a working iconv. Ideally, this test would not require running a test program. For glibc this is easy because it defines __STDC_ISO_10646__, but from the referenced thread I gather that this will never be the case on Solaris. -- 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 prev parent reply other threads:[~2010-12-21 15:26 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-10908-4717@http.sourceware.org/bugzilla/> 2010-12-10 13:34 ` basinilya at gmail dot com 2010-12-21 18:26 ` tromey at redhat dot com [this message] 2009-11-05 14:55 [Bug c++/10908] New: " egor at sun dot com 2009-11-07 1:57 ` [Bug c++/10908] " ppluzhnikov at google dot com 2009-11-07 15:46 ` tromey at redhat dot com 2009-11-07 19:21 ` ppluzhnikov at google dot com 2009-11-07 22:29 ` tromey at redhat dot com 2010-04-19 22:49 ` tromey at redhat 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-10908-4717-u1EykA90fZ@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).