Greg Brown <[email protected]> wrote:
Are you suggesting that the release distribution should include
debug symbols?
Yes.
That would significantly increase the size of the JARs - that may
not be important to a server-side app, but it does have implications
on a client-side app.
It's not that important for desktop apps nowadays, but I see your
point for applets and WebStart apps. However, any serious developer
providing such apps would use pack200 on the jars anyway, and it has
an option --strip-debug to remove any debug symbols. See
http://stackoverflow.com/questions/2287615/java-jar-symbol-info-what-is-the-equivalent-of-tdstrip for
details.
Dirk.
On Apr 16, 2010, at 10:38 AM, Dirk Möbius wrote:
Of course. But do you really want Todd to go "Yikes" again and say
"there's no much you can do"?!?
I don't think there are many open source libraries left without
debugging symbols. Spring has it, Hibernate has it, MyFaces has it.
What's so bad about it?
Dirk.
Greg Brown <[email protected]> wrote:
You can either modify build.xml locally or specify
-Dcompile.debug=true on the command line.
On Apr 16, 2010, at 10:18 AM, Dirk Möbius wrote:
Pivot 1.5pre is still missing debug symbols.
Could you please change build.xml to compile with debug symbols
by default, setting "compile.debug" to true?
Thanks,
Dirk.
Todd Volkert wrote:
Yikes. If you're running off of Pivot 1.4, there's no much you can do,
because debug symbols have been removed from the jars. If you're running
off the trunk, you can compile with debug turned on and get more info.
Can you file an issue in JIRA so we can track this?
Thanks!
-T
On Thu, Apr 1, 2010 at 7:13 PM, Shahzad Bhatti <[email protected]> wrote:
I am seeing following error, but it's not showing my application in the
stack trace. Is there a good way to debug these kind of errors? Thanks.
