From: books at ejurka.com (Kris Jurka) Date: Tue, 20 Nov 2007 11:46:18 -0500 (EST) Subject: [Pljava-dev] Working on 1.4 beta release In-Reply-To: <474306CA.2040005@tada.se> References: <47418556.2070804@tada.se> <474306CA.2040005@tada.se> Message-ID: On Tue, 20 Nov 2007, Thomas Hallgren wrote: > Perhaps an idea would be to provide binary support for the latest, or > the latest two? I.e. if you want older, build your own? > In general this is reasonable, but at the moment I think we need to support 8.1 because it's whats installed/supported on many linux distros. >> Build java code with -g, but pljava c code without debugging symbols I >> reckon. If someone wants to debug pljava C code, they can build it >> themselves. :) >> >> > 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 have some free time over the next few weeks, so I can have a go at >> getting the wiki docs into some kind of source control. > Awesome. Yes, that'd be great. From there it's easy to publish this to http://pljava.projects.postgresql.org. Kris Jurka