RE: [Sablevm-developer] Config File Parsing (Done)

[Brent F. <bre...@xp...>]

> Now, when you build a binary package, for inclusion in an official
> distribution, you simply use some configure options to put 
> files in the right directory, according to the policy of your
> distribution.
> 
> ./configure --prefix=/ --sysconfdir=/etc ...
> 
> I haven't built any binary package for a distribution, yet 
> (except for a Debian kernel package), so I do not know how people
> usually go about it, but I am pretty sure that they do something 
> similar.  Maybe you know more than me about that;-)
> 

Looks like you know about as much as I do :-)

> > 
> > I tried out your test cases, and I'm happy to report that the code
> > does read and store your 3095-byte test string.  Unfortunately, it
> > seems to cause a segfault later on when the JVM attempts to 
> > stat that non-existent directory...
> 
> Have you tested giving sablevm an appropriate boot-class-path and
> boot-library-path?
> 
> It works for me, without segfaulting...
> 

Oh yes -- a valid directory yields a good result.  I'm just saying
that if the user sets garbage in the configuration it does not
recover from this.  (And I'm not sure how far you want to go in
bulletproofing it -- should you protect against the user deleting
the directory after the first read, etc.? ;-))

> I'll let you close the bugs, testing your new privileges:-)
> 
Whee!  Just did it.

-Brent