Date: Sun, 23 Oct 2005 19:49:47 -0600 From: "Manfred Riem" <mriem@manorrock.org> To: freebsd-java@freebsd.org Subject: Re: "An unexpected error" when i run class with constructorcreatingitself. (jdk1.5.0-p2) Message-ID: <djhb21$qko$1@sea.gmane.org> References: <426b510c0510230351k718c38ffr43273a31204414e6@mail.gmail.com><djg3he$k0q$1@sea.gmane.org><17dbe5f00510231618g5e53edebt@mail.gmail.com> <17dbe5f00510231619u1eb684bat@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Steve Joynt" <steve.joynt@gmail.com> wrote in message news:17dbe5f00510231619u1eb684bat@mail.gmail.com... On 24/10/05, Manfred Riem <mriem@manorrock.org> wrote: > This is a completely normal error. You are recursive constructing an > object > in the constructor. This will always generate a StackOverflowError. Since > you are not catching Errors the VM can have a default implementation that > prints out a message (just like it does). I think his point is that in jdk1.4.2-p7 it prints out the StackOverflowError message as expected, but in jdk1.5.0-p2 it core dumps. - steve _______________________________________________ freebsd-java@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-java To unsubscribe, send any mail to "freebsd-java-unsubscribe@freebsd.org" Hi Steve, Whatever the VM will do on an uncaught error is up to the implementation. So dumping the stack trace when hitting a StackOverflowError is well within the specification of the JVM. That it is not the same as in 1.4.2 is something he didn't address. So I stand by my comments of before ;) Kind regards, Manfred Riem mriem@manorrock.org http://www.manorrock.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?djhb21$qko$1>