A few weeks ago, I wrote:
The Kissme in CVS and in the Kissme 0.0.31 release are currently
incompatible with the latest Classpath in CVS ...
Compatibility should be restored in a day or so ...
Last night I fixed the last major bug and checked in a large number of
changes to Kissme. I
/VMThread.currentThread()Ljava/lang/Thread; java/lang/VMThread
Kissme assertion 'hMainThread' failed: vm/startup.c line 383
Attempting to dump core
zsh: abort ./useful_scripts/kissme helloworld
You probably already found out, but for other readers of the list that
try to get Classpath CVS working with Kissme
I've been burned by this mistake before.
To configure kissme I had:
./configure --with-gnu-classpath-install-dir=xxx
but configure ignores an unsupported option, the real option is:
./configure --with-classpath-install-dir=xxx
Because I had classpath 0.06 installed in /usr/lib/classpath etc
Unfortunately I also forgot to make a CVS tag when I released kissme
0.0.31.
... and I've checked in some bug fixes since 0.0.31 :-(
I think we can fix this though. For example, cvs rtag with the -D
option looks like it would do the trick. If that fails, we could
tag the head revisions,
BTW2: I think I'm close to getting Kissme to work with the new Thread
classes anyway.
I did CVS checkouts earlier and everything seems to work perfectly, are
your changes finished?
I'm surprised to hear that. I haven't checked in any of the relevant
Kissme changes yet!
-- Steve
On Tue, 2003-09-02 at 01:31, Stephen Crawley wrote:
Unfortunately I also forgot to make a CVS tag when I released kissme
0.0.31.
... and I've checked in some bug fixes since 0.0.31 :-(
I think we can fix this though. For example, cvs rtag with the -D
option looks like it would do the
The Kissme in CVS and in the Kissme 0.0.31 release are currently
incompatible with the latest Classpath in CVS. The breakage happened
when the new versions of java/lang/Thread.java and vm/reference/java/
lang/VMThread.java were checked in, changing the native method APIs for
threads. [Yeah
This is probably a dumb question, but I re-freshed my Classpath CVS
and updated to kissme 0.31 and kissme isn't working. I get:
Couldn't preallocate OutOfMemoryError exception object
if I pass in any class argument (even for a bogus .class file)
A little mailing list searching turned up
Aaton Renn wrote:
This is probably a dumb question, but I re-freshed my Classpath CVS
and updated to kissme 0.31 and kissme isn't working. I get:
Couldn't preallocate OutOfMemoryError exception object
if I pass in any class argument (even for a bogus .class file)
This is not a dumb
9 matches
Mail list logo
