From: thomas at tada.se (Thomas Hallgren)
Date: Tue, 20 Nov 2007 18:08:26 +0100
Subject: [Pljava-dev] Working on 1.4 beta release
In-Reply-To: <Pine.BSO.4.64.0711201126080.1449@leary.csoft.net>
References: <Pine.BSO.4.64.0711190252450.14611@leary.csoft.net>
	<47418556.2070804@tada.se>
	<ca33c0a30711200643s13204639i37f2a3f57b2e849c@mail.gmail.com>
	<ca33c0a30711200648x6cac4bbfq670fd86667093c38@mail.gmail.com>
	<474306CA.2040005@tada.se>
	<Pine.BSO.4.64.0711201126080.1449@leary.csoft.net>
Message-ID: <4743148A.8060300@tada.se>

Kris Jurka wrote:
>
>
>>>
>> Well, it's not so much about debugging really. It's more the information
>> you can get once something is crashing. As I mentioned, the JVM prints a
>> stack trace that can be very useful. Much is gained if the user who
>> experiences a crash can provide the JVM dump file in a bug-report or
>> attach it to a mailing list posting.
>
> Just to clarify, the java code is never built with -g (see 
> src/java/Makefile.global).  Is there any reason not to change this to 
> always build with -g?
>
I'm not referring to the Java code. The JVM extracts symbolic 
information from the binary. If I'm not mistaking, that information is 
not present when the binary is compiled without -g. If I'm wrong about 
this, then we don't need debugging.

- thomas