This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: GCJ 3.3 c++filt question
- From: Ranjit Mathew <rmathew at hotmail dot com>
- To: java at gcc dot gnu dot org
- Date: Mon, 02 Jun 2003 19:41:27 +0530
- Subject: Re: GCJ 3.3 c++filt question
- References: <000501c32901$c7ef22f0$73dea8c0@lair>
Øyvind Harboe wrote:
When I launch my app, a window quickly appears and goes away again.
Apparently my app launches c++filt
If I remove thisiscool-gcc\gcc-3.3\bin from the path, the window does
not appear(as is what I want on the end user machine). It should be
safe to assume that the end-users do not have c++filt in their path.
I compile with -mwindows, so I'm not sure c++filt makes any sense
anyway.
AFAICT, c++filt is involved in printing out more meaningful stack trace
exceptions.
I assume this is harmless and the intended behaviour even for release
versions of GCJ compiled apps?
Yes, at least as of now.
If you do not want to install c++filt and addr2line for
users, you can actually release only a stripped version of
your program and keep the unstripped binary around for
providing support.
You can then ask the users to send in the error logs
containing mysterious (for them) stack dumps containing
hex addresses and use addr2line/c++filt yourself to
find where the error is.
Ranjit.
--
Ranjit Mathew Email: rmathew AT hotmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/