Re: [kaffe] tomcat

2003-11-30 Thread Dalibor Topic
Hi Ram,

kalyan ram wrote:
Hai
  Can the kaffe virtual machine run the tomcat server?
If there are any special steps,please give me pointers
See the thread at http://www.mail-archive.com/[EMAIL PROTECTED]/msg03287.html

cheers,
dalibor topic
___
kaffe mailing list
[EMAIL PROTECTED]
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe


Re: [kaffe] DocBook and Maven proposal

2003-11-30 Thread Michael Franz

--- Jim Pick [EMAIL PROTECTED] wrote:
 Hi,
 
 I'm trying to figure out a good way of integrating
 better documentation
 into the project.
 
Cool. 
snip 
 Additionally, we want to support generating and
 shipping Javadoc
 documentation (probably using gjdoc as our Javadoc
 implemention).

I have been thinking about this for the past few days,
however I am interested in documenting the C code that
makes up Kaffe.  I am familiar with HeaderDoc from
Apple and have been looking at GPL alternatives.  I
have found Doxygen that seems to be very complete and
has been used in a number of projects.
http://www.stack.nl/~dimitri/doxygen/ Here is a list
of other free source code documentation tools.
http://www.stack.nl/~dimitri/doxygen/links.html


I took a brief look at gjdoc, but there is only the
cvs code.  What will be the feature set of gjdoc?

Michael

__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

___
kaffe mailing list
[EMAIL PROTECTED]
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe


Re: [kaffe] DocBook and Maven proposal

2003-11-30 Thread Jim Pick
On Sun, 30 Nov 2003 08:10:43 -0800 (PST)
Michael Franz [EMAIL PROTECTED] wrote:

 I have been thinking about this for the past few days,
 however I am interested in documenting the C code that
 makes up Kaffe.  I am familiar with HeaderDoc from
 Apple and have been looking at GPL alternatives.  I
 have found Doxygen that seems to be very complete and
 has been used in a number of projects.
 http://www.stack.nl/~dimitri/doxygen/ Here is a list
 of other free source code documentation tools.
 http://www.stack.nl/~dimitri/doxygen/links.html

I haven't played with it yet, but Doxygen is extremely popular -- I know
we use it at the place I work.  I think that would be a safe one to go
with.  I'm encouraged that there also seems to be a Maven plugin for it:

  http://maven-plugins.sf.net/maven-doxygen-plugin/

So, theoretically, we can plug it into our Maven-based documentation
generation system.  Again, I expect that we may have to modify a few
Maven plugins and put them in kaffe-extras to get the exact output we
want for the published tarballs and the website.

 I took a brief look at gjdoc, but there is only the
 cvs code.  What will be the feature set of gjdoc?

I'll have to let someone else answer that, as I haven't played with it
yet.  I'm hoping it's got the basic Javadoc features so that we use it
as our Javadoc, and use it with tools such as Ant and Maven.  I think
some IDEs parse the generated HTML documentation, so that might be one
tricky area for compatibility to watch out for.

One more thing I forgot to mention in the proposal - some ideas I have
for the documentation development process:

 1) I want to keep as much development on the mailing list as possible.

 2) I'm thinking of moving the website over to Tomcat - so we can add   
various webapps to it to do some interesting things.

 3) I've got a half-done regression testing system I would like to
deploy on the website.  I'd like to hook that into the documentation
generation system somehow -- primarily so that the documentation
can say things like Application XYZ version 1.2.3 passed basic
regression tests on Platform XX with Kaffe x.y.z.  If we can
say things like that, then we'll get users for our future
production releases.

 4) Even though I want all the discussion to happen on-list, I'm
starting to think that a Wiki might be useful.  It could be used
to store various bits of quickly mutating information, or for
editing drafts of half-baked documentation before we commit it
into CVS.  Opinions?

Anyways, I've got too many ideas - it's slowing me down.  :-)

Cheers,

 - Jim

___
kaffe mailing list
[EMAIL PROTECTED]
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe


Re: [kaffe] DocBook and Maven proposal

2003-11-30 Thread Dalibor Topic
Michael Franz wrote:
I haven't played with it yet, but Doxygen is
extremely popular -- I know
we use it at the place I work.  I think that would
be a safe one to go
with.  I'm encouraged that there also seems to be a
Maven plugin for it:
 http://maven-plugins.sf.net/maven-doxygen-plugin/

So, theoretically, we can plug it into our
Maven-based documentation
generation system.  Again, I expect that we may have
to modify a few
Maven plugins and put them in kaffe-extras to get
the exact output we
want for the published tarballs and the website.


Ok, I will start to document the stuff I am interested
in using Doxygen.  If the Kaffe developers start to
use it, then I will be ahead of the game, otherwise, I
will still benefit from it.
Yeah, using doxygen makes a lot of sense. I'm using doxygen comments on 
things I fix/change in the C files as well.

cheers,
dalibor topic
___
kaffe mailing list
[EMAIL PROTECTED]
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe


[kaffe] CVS kaffe (dalibor): Added support for GNU Crypto

2003-11-30 Thread Kaffe CVS
PatchSet 4174 
Date: 2003/11/30 23:49:11
Author: dalibor
Branch: HEAD
Tag: (none) 
Log:
Added support for GNU Crypto

Members: 
ChangeLog:1.1766-1.1767 
Makefile.am:1.49-1.50 
Makefile.in:1.117-1.118 
aclocal.m4:1.71-1.72 
configure:1.265-1.266 
configure.in:1.231-1.232 
gnu-crypto.m4:INITIAL-1.1 
config/Makefile.in:1.91-1.92 
developers/update-class-list:1.8-1.9 
include/Makefile.in:1.126-1.127 
kaffe/Makefile.in:1.83-1.84 
kaffe/jvmpi/Makefile.in:1.8-1.9 
kaffe/kaffe/Makefile.in:1.97-1.98 
kaffe/kaffeh/Makefile.in:1.84-1.85 
kaffe/kaffevm/Makefile.in:1.116-1.117 
kaffe/kaffevm/gcj/Makefile.in:1.65-1.66 
kaffe/kaffevm/intrp/Makefile.in:1.73-1.74 
kaffe/kaffevm/jit/Makefile.in:1.79-1.80 
kaffe/kaffevm/jit3/Makefile.in:1.49-1.50 
kaffe/kaffevm/systems/Makefile.in:1.75-1.76 
kaffe/kaffevm/systems/beos-native/Makefile.in:1.66-1.67 
kaffe/kaffevm/systems/oskit-pthreads/Makefile.in:1.72-1.73 
kaffe/kaffevm/systems/unix-jthreads/Makefile.in:1.75-1.76 
kaffe/kaffevm/systems/unix-pthreads/Makefile.in:1.45-1.46 
kaffe/man/Makefile.in:1.73-1.74 
kaffe/scripts/Makefile.in:1.106-1.107 
kaffe/scripts/bat/Makefile.in:1.66-1.67 
kaffe/scripts/compat/Makefile.in:1.89-1.90 
kaffe/xprof/Makefile.in:1.41-1.42 
libraries/Makefile.in:1.70-1.71 
libraries/clib/Makefile.in:1.76-1.77 
libraries/clib/awt/Makefile.in:1.83-1.84 
libraries/clib/awt/X/Makefile.in:1.73-1.74 
libraries/clib/awt/qt/Makefile.in:1.28-1.29 
libraries/clib/io/Makefile.in:1.76-1.77 
libraries/clib/management/Makefile.in:1.85-1.86 
libraries/clib/math/Makefile.in:1.81-1.82 
libraries/clib/native/Makefile.in:1.108-1.109 
libraries/clib/net/Makefile.in:1.89-1.90 
libraries/clib/nio/Makefile.in:1.2-1.3 
libraries/clib/security/Makefile.in:1.49-1.50 
libraries/clib/security/java.security:1.2-1.3 
libraries/clib/zip/Makefile.in:1.83-1.84 
libraries/extensions/Makefile.in:1.61-1.62 
libraries/extensions/comm/Makefile.in:1.56-1.57 
libraries/extensions/comm/javalib/Makefile.in:1.56-1.57 
libraries/extensions/microsoft/Makefile.in:1.48-1.49 
libraries/extensions/microsoft/clib/Makefile.in:1.51-1.52 
libraries/extensions/microsoft/javalib/Makefile.in:1.49-1.50 
libraries/extensions/pjava/Makefile.in:1.56-1.57 
libraries/extensions/pjava/javalib/Makefile.in:1.56-1.57 
libraries/extensions/servlet/Makefile.in:1.56-1.57 
libraries/extensions/servlet/javalib/Makefile.in:1.56-1.57 
libraries/extensions/sound/Makefile.in:1.24-1.25 
libraries/extensions/sound/alsa/Makefile.in:1.26-1.27 
libraries/extensions/sound/common/Makefile.in:1.26-1.27 
libraries/extensions/sound/esd/Makefile.in:1.26-1.27 
libraries/javalib/Makefile.in:1.193-1.194 
replace/Makefile.in:1.20-1.21 
test/Makefile.in:1.76-1.77 
test/internal/Makefile.in:1.30-1.31 
test/regression/Makefile.am:INITIAL-1.84 
test/regression/Makefile.in:1.139-1.140 
test/regression/TestGnuCrypto.java:INITIAL-1.1 
test/regression/TestScript.in:1.40-1.41 
test/regression/compile_time/Makefile.in:1.4-1.5 
test/regression/run_time/Makefile.in:1.4-1.5 

Index: kaffe/ChangeLog
diff -u kaffe/ChangeLog:1.1766 kaffe/ChangeLog:1.1767
--- kaffe/ChangeLog:1.1766  Fri Nov 28 16:15:16 2003
+++ kaffe/ChangeLog Sun Nov 30 23:49:11 2003
@@ -1,3 +1,87 @@
+2003-11-29  Dalibor Topic [EMAIL PROTECTED]
+
+   * Makefile.in,
+   aclocal.m4,
+   config/Makefile.in,
+   configure,
+   include/Makefile.in,
+   kaffe/Makefile.in,
+   kaffe/jvmpi/Makefile.in,
+   kaffe/kaffe/Makefile.in,
+   kaffe/kaffeh/Makefile.in,
+   kaffe/kaffevm/Makefile.in,
+   kaffe/kaffevm/gcj/Makefile.in,
+   kaffe/kaffevm/intrp/Makefile.in,
+   kaffe/kaffevm/jit/Makefile.in,
+   kaffe/kaffevm/jit3/Makefile.in,
+   kaffe/kaffevm/systems/Makefile.in,
+   kaffe/kaffevm/systems/beos-native/Makefile.in,
+   kaffe/kaffevm/systems/oskit-pthreads/Makefile.in,
+   kaffe/kaffevm/systems/unix-jthreads/Makefile.in,
+   kaffe/kaffevm/systems/unix-pthreads/Makefile.in,
+   kaffe/man/Makefile.in,
+   kaffe/scripts/Makefile.in,
+   kaffe/scripts/bat/Makefile.in,
+   kaffe/scripts/compat/Makefile.in,
+   kaffe/xprof/Makefile.in,
+   libraries/Makefile.in,
+   libraries/clib/Makefile.in,
+libraries/clib/awt/Makefile.in,
+libraries/clib/awt/X/Makefile.in,
+libraries/clib/awt/qt/Makefile.in,
+libraries/clib/io/Makefile.in,
+libraries/clib/management/Makefile.in,
+libraries/clib/math/Makefile.in,
+

Re: [kaffe] DocBook and Maven proposal

2003-11-30 Thread Michael Franz
Now that I am fooling around with doxygen, I found
that it can actually provide some documentation
without the special tags.  It is actually a good
starting point for understanding the API with Kaffe. 
Once the tags are added, the documentation will make
it easier to understand what different methods do.

It also understands the JavaDoc tags, so, do we use
the C tags or stick with the JavaDoc tags?

 Yeah, using doxygen makes a lot of sense. I'm using
 doxygen comments on 
 things I fix/change in the C files as well.
 
 cheers,
 dalibor topic
 
 
Michael

__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

___
kaffe mailing list
[EMAIL PROTECTED]
http://kaffe.org/cgi-bin/mailman/listinfo/kaffe


[kaffe] SIGSEGV on kaffe mipsel

2003-11-30 Thread Mark and Janice Juszczec
Hi folks

In an effort to track down my SIGSEGV, I recompiled kaffe for mipsel with 
--enable-debug.  When I run on my Helio pda, I get the output at the end of 
the email.

Its late on Sunday and I wanted to post it before I signed off and forgot.  
I'll do some analysis on it tomorrow.

On a related subject, I need advice about debugging kaffe remotely.  I'd 
like to run gdb on my i386 laptop, run kaffe on my mipsel pda and debug 
mipsel kaffe from my laptop.  Can anyone point me to READMEs, FAQs or HOWTOs 
on the web?

Thanks

Mark



# kaffe-bin -vmdebug ALL FirstClass
You cannot debug the JIT in interpreter mode
pagealloc(5242880) = (nil)
gc_system_alloc: 5242880 byte at (nil)
pagealloc(1048576) = 0x10016000
1048576 unused bytes in heap addr range
gc_system_alloc: 1048576 byte at 0x2aaab008
gc_primitive_free: Prepending (1048576,0x2aaab008) beginning of freelist
gc_primitive_alloc: 4096 bytes from freelist @ 0x2aaab008
gc_heap_malloc: small block 56 at 0x2aaab008 free 0x10016090
gc_primitive_alloc: 16384 bytes from freelist @ 0x2aaab030
gc_heap_malloc: freelist 56 at 0x2aaab008 free 0x100160c8
gc_primitive_alloc: 4096 bytes from freelist @ 0x2aaab0d0
gc_heap_malloc: small block 328 at 0x2aaab0d0 free 0x1001b010
allocating new thread, stack base 0x1001b148-0x1001b148
resumeThread 0x1001b018
disable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_primitive_alloc: 4096 bytes from freelist @ 0x2aaab0f8
gc_heap_malloc: small block 36 at 0x2aaab0f8 free 0x1001c0c8
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_primitive_alloc: 8192 bytes from freelist @ 0x2aaab120
gc_heap_malloc: large block 4104 at 0x1001d008
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_primitive_alloc: 4096 bytes from freelist @ 0x2aaab170
gc_heap_malloc: small block 13 at 0x2aaab170 free 0x1001f1c8
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_malloc: freelist 40 at 0x2aaab0f8 free 0x1001c0f0
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_malloc: freelist 40 at 0x2aaab0f8 free 0x1001c118
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_malloc: freelist 16 at 0x2aaab170 free 0x1001f1d8
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_primitive_alloc: 4096 bytes from freelist @ 0x2aaab198
gc_heap_malloc: small block 26 at 0x2aaab198 free 0x100200f0
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_malloc: freelist 26 at 0x2aaab198 free 0x10020110
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_malloc: freelist 14 at 0x2aaab170 free 0x1001f1e8
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_primitive_alloc: 4096 bytes from freelist @ 0x2aaab1c0
gc_heap_malloc: small block 18 at 0x2aaab1c0 free 0x10021140
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_primitive_alloc: 4096 bytes from freelist @ 0x2aaab1e8
gc_heap_malloc: small block 1032 at 0x2aaab1e8 free 0x10022008
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_free: memory 0x10022008 size 2016
disable stop for thread  0x1001b018
gc_primitive_free: Merging (4096,0x2aaab1e8) beginning of freelist
enable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_malloc: freelist 52 at 0x2aaab008 free 0x10016100
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_free: memory 0x10016100 size 56
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_free: memory 0x1001f1e8 size 16
disable stop for thread  0x1001b018
enable stop for thread  0x1001b018
enable stop for thread  0x1001b018
disable stop for thread  0x1001b018
gc_heap_free: memory 0x10021140 size 24
disable stop for thread  0x1001b018
gc_primitive_free: Merging (4096,0x2aaab1c0) beginning of freelist
enable stop for thread  0x1001b018
enable stop for thread