weird error messages from gcc and g++ when using cygwin

Hi all,

recently I'm having some troubles with gcc and g++ while  compiling
my codes on a linux remote machine,
which I log in from a windows box through cygwin.
Everything appears to work fine except for some odd and annoying
behaviour of the compilers
(or, I suspect, of cygwin).

Whenever I make something stupid the compilers very efficiently point
it out to me, but the detailed
information about the error I've made gets lost at some point.
Let me make an example: suppose I use an undefined variable "v"  at
line 10 of "code.c",
in a  function called "Hallo". The good compilers used to tell me
something like:

code.c: In function Hallo:
code.c:10: error: v undeclared (first use in this function)
code.c:10: error: (Each undeclared identifier is reported only once
code.c:10: error: for each function it appears in.)

Recently they started telling

code.c: In function â:
code.c:10: error: â undeclared (first use in this function)
code.c:10: error: (Each undeclared identifier is reported only once
code.c:10: error: for each function it appears in.)

that is, the function and variable name are somehow lost, and a
character "â" appears instead
of them in the error message. This is not the end of the world, but it
is quite annoying.

A friend works locally on the remote linux machine, and he says that
the (same) compilers do
not exhibit the above weird behavior. Hence I thought the problem
might be in some cygwin setting.
Actually I just logged in from a linux machine, and there is no
problem with the error messages.
However, cygwin terminals are not the only ones to exhibit the strange
message problem: I get it
also when I log in from windows, using "ssh Secure Shell client".
Has anybody a clue about what the problem (and the solution) might
be?

Thanks a lot

Francesco
[ Auf dieses Posting antworten ]