agora inbox for pljava-dev@postgresql.org  

help / color / mirror / Atom feed

Subject: [Pljava-dev] Working on 1.4 beta release
Date: Tue, 20 Nov 2007 11:46:18 -0500 (EST)
Message-ID: <Pine.BSO.4.64.0711201126080.1449@leary.csoft.net> (raw)
In-Reply-To: <474306CA.2040005@tada.se>
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>



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

view thread (9+ messages)  latest in thread

Message-ID: <Pine.BSO.4.64.0711201126080.1449@leary.csoft.net>
Permalink:  ../Pine.BSO.4.64.0711201126080.1449@leary.csoft.net/
Also on:    postgresql.org/message-id/Pine.BSO.4.64.0711201126080.1449@leary.csoft.net

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pljava-dev@postgresql.org
  Subject: Re: [Pljava-dev] Working on 1.4 beta release
  In-Reply-To: <Pine.BSO.4.64.0711201126080.1449@leary.csoft.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox