Re: [Aegisvm-devel] Re: patch to add debug info to printStackTrace

[Gildas B. <gb...@al...>]

On Wednesday 24 July 2002 23:58, Philip Fong wrote:
> Hi Gildas
> 
> Yes, this is definitely useful.  This is going to help debugging a lot.
> I've just skimmed through the code a bit, and it looks okay.  So, out of
> which version (or CVS tag) is you patch made.  I'll need this in order
> to actually integrate your code into the CVS.

I like to live on the bleeding edge so I'm always using an up to date CVS :)

> I think what I will do is to add a configure switch so that your new
> feature is on by default, and for those who really want to reduce class
> size when the VM is deployed, they can choose to turn off the feature.
> What do you think?

Humm, I'm not sure I understand you there.

The only overhead that this patch adds in terms of memory usage is that it 
stores an additional ju2 field in AEClass to keep the index of the java 
source file name in the constant pool. And another additional 2 fields in 
AEMethod to store an array of line numbers and pc correspondance and the 
size of this array.

Which means that only the additional array will really create an overhead, 
but this array will be allocated only if the bytecode class file actually 
contains the line numbers debug info.
If the user doesn't want this overhead than it should be up to him to 
compile the java source code without this debug info.

( that reminds me that "method->lines_count" and "method->lines" are not 
properly initialised to 0 in the patch I sent you. I'll send you an updated 
version )

> If you are tracking the CVS, you'll notice that I am doing quite a 
> bit of restructuring recently.  Would you like to subscribe to
> the development mailing list so that you can be kept up to date
> about when it is a good time to synchronize your code with the CVS
> repository?
> 

Sorry for confusing you, I'm already subscribed it's just that I didn't send 
this email from the mail account which I used to suscribe.

Regards,

--
Gildas