This is the mail archive of the
java-prs@gcc.gnu.org
mailing list for the Java project.
[Bug libgcj/20508] gij prints too much information if an incorrect class is given
- From: "mark at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: java-prs at gcc dot gnu dot org
- Date: 17 Mar 2005 10:30:34 -0000
- Subject: [Bug libgcj/20508] gij prints too much information if an incorrect class is given
- References: <20050317022236.20508.mckinlay@redhat.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From mark at gcc dot gnu dot org 2005-03-17 10:30 -------
Note that I made it more verbose then it was in the past on purpose.
But not for this case. See an example of a stacktrace were (most) of this
"extra" information is useful:
http://gcc.gnu.org/ml/java-patches/2005-q1/msg00337.html
This really helps when debugging strange reasons for your main class not wanting
to start correctly.
When cleaning this up be careful to at least keep the root cause and the
classloaders and search paths used. And when the root cause is some (chained)
ExceptionInInitializerError inside some super or interface class needed by the
main class you really want the stacktrace to track down why/what happened where.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20508