Ahh...this may be a solution. It looks like I could build it to not do mmap()s, but do malloc()s instead by using -DUSE_MALLOC (and maybe even link it against hoard to have a really nice malloc)
However, it appears to be a total pain to get this thing to compile... I have no idea where a JDK with libjvm_g.so comes from and OPEN_MAX wasn't defined in some file and my yacc didn't like line 125 of parser.y and signals_md.o has a bunch of unresolved symbols that should be in threads_md.o Seems like if I actually reverted to the version of GCC they recommend it might fix some of these problems, but I don't think all. Does anyone actually compile this thing? :) Someone want to help me with getting one that has -DUSE_MALLOC? eric. On Tue, Feb 12, 2002 at 02:24:40PM -0500, Paul Mclachlan wrote: > At :47 02 Feb 2002 -0600, Eric wrote: > > > Does anyone have any idea how to fix this? Would it be a big job to > > fix it in the JVM? > > You could grab the source to 1.3.1 at: > > http://www.sun.com/software/communitysource/ > > and edit > > jdk131src/j2sdk1.3.1/src/solaris/hpi/src/memory_md.c > > to use your own allocation strategy. All of the platform specific stuff the VM > does goes through HPI, I'm pretty sure this would work & it doesn't seem like > too much work... > > - Paul -- _____ _ | ____|(_) http://ir.iit.edu/~ej | _| | | Research Assistant | |___ | | Information Retrieval Laboratory |______/ | Illinois Institute of Technology |__/ ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
