Re: awt problem on darwin

[Bryce McKinlay <bryce at waitaki dot otago dot ac dot nz>]

Andreas Tobler wrote:

>> The stack trace may take some hacking to implement on Darwin, but 
>> Throwable.printStackTrace should at least calling toString() on the 
>> exception object that got thrown - its a bug if it isn't.
>
>
> I'll have a look at. There are other things I want find out. E.g. the 
> options stuff in gij. This seems to me a bit bogus. I was playing with 
> heapsize and found out that it throwss exceptions or doesn't get the 
> value in. 


Yeah, its possible that it doesn't work any more. What I really want is 
some unified infrastructure for passing VM arguments and properties to 
libgcj at runtime. The same code should be used to parse arguments for 
gij, normal binary libgcj apps (via an environment variable), and the 
vm_args parameters for the invocation interfaces. It should be able to 
be used to control things like initial/maximum heap as well as turn on 
debugging options - basically the same things that you can control from 
the command line to a regular Java VM.

Nic Ferrier, I think, indicated that he was working on something like 
this. Did you make any progress with that Nic?

regards

Bryce.