Bug 157206 - class name appears as A in error messages
class name appears as A in error messages
Product: Fedora
Classification: Fedora
Component: gcc4 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2005-05-09 08:43 EDT by Robert J. Nichols
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-10 05:45:11 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert J. Nichols 2005-05-09 08:43:39 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0; T312461)

Description of problem:
Information in error messages produced by gcc 4.0.0 in fc4test2 is being represented by the character  on my machine e.g.

/public/test.cpp:92:error: Â has no member named Â

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Reference a missing class member

Actual Results:  The following error message is generated
/public/test.cpp:92: error  has no member named Â

Expected Results:  name of class and member should have appeared in the error message

Additional info:
Comment 1 Jakub Jelinek 2005-05-10 03:29:19 EDT
Please provide a self-contained testcase.
Comment 2 Jakub Jelinek 2005-05-10 05:45:11 EDT
"gcc output shows hex codes e2 80 in the message which is causing the

Your terminal setup is wrong then.  If you are running GCC in UTF-8 locale
(such as en_US.UTF-8), it prints the opening/closing quotes as UTF-8 non-ASCII
characters (\xe2\x80\x98 and \xe2\x80\x99).
If your terminal can't handle this and can't be changed to grok that, you should
not run programs in UTF-8 locale.  In say en_US locale (or C locale) GCC will use
' as both opening and closing quote.

Note You need to log in before you can comment on or make changes to this bug.