Your message dated Sat, 6 May 2006 12:19:02 +0200
with message-id <[EMAIL PROTECTED]>
and subject line corrupted error messages
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gcc-4.0
Version: 4.0.2-5
Severity: important
gcc gives corrupted(?) error messages:
% cat x.c
void main()
{
x = 1;
}
% gcc x.c
x.c: In function \uffff:
x.c:4: error: \uffff undeclared (first use in this function)
x.c:4: error: (Each undeclared identifier is reported only once
x.c:4: error: for each function it appears in.)
x.c:3: warning: return type of \uffff is not \uffff
The \uffff didn't cut and paste very well on my terminal it is just a
funny box as if it was a binary or unprintable character.
I will also note that I grabbed gcc-4.1 from experimental and had the
exact same issue.
Rick
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages gcc-4.0 depends on:
ii binutils 2.16.1cvs20051214-1 The GNU assembler, linker and bina
ii cpp-4.0 4.0.2-5 The GNU C preprocessor
ii gcc-4.0-base 4.0.2-5 The GNU Compiler Collection (base
ii libc6 2.3.5-8.1 GNU C Library: Shared libraries an
ii libgcc1 1:4.1-0exp7 GCC support library
Versions of packages gcc-4.0 recommends:
ii libc6-dev 2.3.5-8.1 GNU C Library: Development Librari
pn libmudflap0-dev <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.0.3-2
> Hi, I've seen this in the past; it seems to be that gcc is trying to
> use 'smart quotes' when in a unicode locale. However, with gcc
> 4.0.3-2 I cannot reproduce it; it may have been fixed/changed at some
> point.
closing the report
--- End Message ---
