Giuseppe Bux wrote: > Ryan, the "-e" parameter edited just after the mvn commands did not > produce any extended trace. So I browsed the StackOverflowError on > the web at the following site: > http://java.sun.com/j2se/1.4.2/docs/api/java/lang/StackOverflowError.html
Right, I keep forgetting Windows terminology. I suppose it should be a '/e' instead of the Unix '-'. Are you using 1.5 or 1.4? > Here you can read that the stack overflow occurs because an > application recurses too deeply. It recurses too deeply on one particular stack, yours. It doesn't on my Windows machine. The default stack size should be the same, which is why we need more data about your environment. I can't reproduce your error, so I need your debugging to understand whether it's something we can fix or not. > Moreover in the Constructory Summary of the class error you can read > that this, edited without the (string) paramater, do not produce > error details: this could explain the lack of extended trace although > the -e parameter after the mvn commands. The -e (/e) switch should gives the entire stack trace regardless - it's a snapshot of the virtual machine to find out where in the application the error is taking place. It doesn't have anything to do with how the error is built, which is just the end of the stack. Aain, my thanks; hopefully Longwell will come out of this discussion the better for it. -- Ryan Lee [EMAIL PROTECTED] MIT CSAIL Research Staff +1.617.253.5327 http://simile.mit.edu/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
