echidna-interest Mailing List for Echidna
Brought to you by:
lukeg
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Steck Jean-P. <jp...@el...> - 2002-02-08 13:58:19
|
Hello, I'm currently developping a project with swing. We have a big problem with what sun calls bug id=4080029 : See <http://developer.java.sun.com/developer/bugParade/bugs/4080029.html> "a modal dialog block input to all frame windows not just its parent". I've read on a forum that the class AppContext can help to associate a distinct awt-thread with every distinct swing application running in the same JVM. http://altair.cs.oswego.edu/pipermail/javares/2000-March/000003.html But I found that this class is not documented and I really have no idea how to use this AppContext. Then I found your project. I've tried to run my applications with echidna, but the result was still the same. But anyway, it might be someone in this list that knows about AppContext, or better about bug id=4080029. Sorry to use this diffusion list in my personal interest. Thanks to anyone who can help !! Best regards. Jean-Philippe Steck |
From: Stefan R. <do...@dr...> - 2001-07-21 17:44:31
|
Hi Luke, I would like to suggest an Echidna patch (it's enclosed as a diff against recent CVS). This patch actually combines two unrelated changes: 1. It solves a bug in ProcessGarbageCollector.wakeUp(). I may be wrong here, but I think it should call notifyAll() on _rootGroup rather than on the ProcessGarbageCollector itself. Without the patch, when I called System.exit in an Echidna process, other threads that waitFor() that process took a few seconds before they woke up. With the patch applied, this happened instantly. 2. It introduces a new method void setAllowSystemExit(boolean flag) in ProcessManager. It is a flag that tells whether System.exit() will kill the current Echidna process (flag==false) or actually exit the whole VM (flag==true). The advantage is that you can specify an exit code for the whole program. The old method via ERRORCODE_BYPASS_SECURITY didn't allow this. (I actually removed that constant and changed ProcessManagerFrame to use the new method.) The reason why I am messing with Echidna is that I am currently developing a patch for the Jakarta Ant tool to incorporate Echidna. Ant build scripts often fork new VMs because some Java code needs to be executed different classpath. This is of course rather inefficient. Using custom class loaders and a little bit of "magic code" for System.out and System.exit, it should be possible to execute that code in the same VM Ant itself runs in. Luckily, Echidna provides all this. I was already able to Echidna-ize a few forked calls in my Ant scripts. There are still bugs to rule out though... Provided the Ant patch makes its way into the Ant distribution, it will be good if it can work with an off-the-shelf Echidna. Returning a meaningful exit code is essential for Ant, so it will be good if Echidna is changed as I suggested (or in a similar way). I am very interested in your feedback. Best, -Stefan |
From: Stefan R. <do...@dr...> - 2001-07-15 12:32:13
|
Hi Luke et al, I really like Echidna and the fact that it's getting into active = development again. I would like to make a feature suggestion. It would be great if Echidna = could safely and cleanly terminate Java threads. A way to do this in = pure java is described here: http://citeseer.nj.nec.com/433897.html However, their method relies on rewriting byte codes and has a = noticeable performance impact (they introduce polls of a termination = flag throughout the application code).=20 With a VM that supports a recent version of the Java Platform Debugger = Architecture ( http://java.sun.com/products/jpda/ ), it might be = possible to achieve the same effect without a perfomance impact (while = remaining VM-independent). JPDA allows to inspect and change stack = frames; when the termination of a thread is requested, Echidna could use = JPDA to modify the thread's stack and effectively force it to exit. What do you think? Best, -Stefan |
From: Luke G. <lu...@bl...> - 2001-06-12 13:04:59
|
Hi Timothy, > I see that you list the status as post-alpha, and stable. Why > no 1.0 release? This looks to be a very nice application, but I can't > use anything that is not production; no beta. Ahh, the ol' version naming problem :-). Echidna has been in serious use for about 4 years and as far as I know works properly, within its known limitations. The 0.4.0 version number is perhaps a bit on the "conservative" side, and is fairly arbitrary. I did put the "post-alpha" "stable" rating on SourceForge in good faith. So I would recommend that you try it and see how it goes. > Can you give any info on what is upcomming? Thanks. Echidna has historically not been continuously developed, and there was a pretty long "dry spell" recently. But now I've imported my working directory (which contained various changes submitted over the past year or two) into SourceForge, and Rocky Burt has recently been making a lot of improvements (particularly to the GUI). I think there are enough changes to make a new release now. Whether to call it 0.5, 1.0, or e-Chidna 2001 Enterprise Edition is something I'll have to ask my marketing department about ;-) Historical note: Versions to date have been alpha-1, alpha-2, alpha-3, 0.4.0. If I were to choose the version that I think matches the usual "1.0" connotations, it would probably be alpha-3, which was the first release after other people started hacking on it aswell. Cheers, Luke |
From: Timothy R. <tr...@si...> - 2001-06-12 00:49:50
|
I see that you list the status as post-alpha, and stable. Why no 1.0 release? This looks to be a very nice application, but I can't use anything that is not production; no beta. Can you give any info on what is upcomming? Thanks. |
From: Luke G. <lu...@bl...> - 2001-06-07 19:51:04
|
I've imported some new code into the sourceforge CVS tree. See http://www.javagroup.org/echidna/ for details. Cheerio, Luke |
From: Luke G. <lu...@bl...> - 2001-06-07 17:28:24
|
Hallo. |