Logging broken ?

Wed Apr 6 12:52:00 GMT 2005

> now I compiled with
>> gcj -Dgnu.gcj.runtime.NameFinder.remove_unknown=true -g \

I feel silly for this typo - that should have
been "false" instead of "true" (which is the
default value). Sorry for that.
> Is there an easy way to send the standard out from hello.exe to the
> c++filt appilcation in a WindowsXP command shell (cmd.exe) window ?

For standard *output* piping via the "|" works just
as well in Windows. E.g. "echo foo | bar" will make
"foo" appear in "bar"'s standard input. I do not know
how to redirect standard *error* though.
> As I'm still trying to fnd a way to use the gdb i just downloaded the
> Manual, maybe I can find out how to use it, eventhough I'm not expecting
> revolutionary new insights.

Don't hold your breath - it will not be useful 
if the libgcj runtime does not have debugging
information. Mohan does not distribute 
libgcj with debugging information IIRC as
the resultant binary otherwise is *huge* and
would strain his bandwidth, not to mention
increase download times for users.
Your best bet would be to either build
GCJ with debugging information yourself
or wait for a Win32 maintainer (i.e. Mohan)
to figure out the problem (which might
or might not happen anytime soon as it is
a volunteer effort by people who mostly
do something else for a living).
On the other hand, if you have some
time, you can build GCJ for Win32
yourself by following the steps given
in:
http://ranjitmathew.hostingzero.com/phartz/gcj/bldgcj.html
NOTE: The mkXXX.sh scripts used in that
article explicitly strip out debugging
information (using "-g0"), so you should
remove the use of this flag everwhere in
those scripts before proceeding.
HTH,
Ranjit.
-- 
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.hostingzero.com/