Re: File.getAbsolutePath() bugfix
On Thu, Jan 13, 2000 at 02:37:13PM -0500, Mike Linksvayer wrote: Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath() is correct, only getCanonicalPath() is incorrect. I'll post a real fix tonight, after I've tested more thoroughly. It happens that getCanonicalPath was fixed on January 4. Luck would have it that I was working with code I retreived on January 3. I had assumed that cvs diff would give me differences between the head revision and my file, but apparently it gives the differences between the revision I have checked out and my file ... I haven't used cvs in two years. :( Now I've encountered another problem: Process.destroy() causes kaffe to exit without a stack trace and without a core file. The following simple program never prints "destroyed" on my system (Debian 2.1, kernel 2.2.1, gcc 2.7.2.3). public class destroy { public static void main(String[] args) { try { System.err.println("starting process"); Process p = Runtime.getRuntime().exec("sleep 5"); System.err.println("started process, destroying"); p.destroy(); System.err.println("destroyed process"); } catch (Throwable t) { t.printStackTrace(); } } } I haven't tried running in gdb yet. Another question: Is it safe to use gcc 2.95? http://www.kaffe.org/trouble.html says egcs is not ok, but that's dated 4/99, and I've read about experimental gcj support which obviously would require egcs. I ask because I've tried very briefly to compile and run kaffe on Solaris and Suse systems and egcs with bad results. -- See From: and Organization: above.
Re: File.getAbsolutePath() bugfix
On Jan 14, 2000, "Edouard G. Parmelan" [EMAIL PROTECTED] wrote: I see, pid is not saved after fork. Fixed now, thanks. BTW, waitpid doesn't load pid either :-( -- Alexandre Oliva http://www.ic.unicamp.br/~oliva IC-Unicamp, Bra[sz]il oliva@{lsd.ic.unicamp.br,guarana.{org,com}} aoliva@{acm,computer}.org oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org} ** I may forward mail about projects to mailing lists; please use them
Re: File.getAbsolutePath() bugfix
Alexandre Oliva wrote: I see, pid is not saved after fork. Fixed now, thanks. BTW, waitpid doesn't load pid either :-( Okay, I will fix that too, but I have to check KWAITPID() also. For exemple in unix-jthread(), it loop on error (with a comment) but on BeOS, it return the error :( I will look that this WE. -- Edouard G. Parmelan http://egp.free.fr
Re: File.getAbsolutePath() bugfix
Thanks, fixed! Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath() is correct, only getCanonicalPath() is incorrect. I'll post a real fix tonight, after I've tested more thoroughly. I must learn not to: * think code is finished before writing unit tests * think code is fixed if it fixes my particular problem * watch over a locksmith fixing my front door while debugging (really) Sorry about that. -- See From: and Organization: above.
Re: File.getAbsolutePath() bugfix
Mike Linksvayer writes: Thanks, fixed! Argh, please unfix. I'm an idiot ... the behavior of getAbsolutePath() is correct, only getCanonicalPath() is incorrect. I'll post a real fix tonight, after I've tested more thoroughly. OK, unfixed! :-) -Archie ___ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com