On Wed, 2005-11-09 at 14:12 -0600, Archie Cobbs wrote:
> Stuart Ballard wrote:
> > Seems like we could remove VMClass.getClassLoader altogether then
> > since it's public and static in VMStackWalker?
>
> Yes, I suppose so...
I can imagine a vm optimizing VMClass.getClassLoader() differently from
Stuart Ballard wrote:
Seems like we could remove VMClass.getClassLoader altogether then
since it's public and static in VMStackWalker?
Yes, I suppose so...
> On the other hand,
should it be public in VMStackWalker? Is that ok from a security
standpoint?
Yes.. all the other methods in there
Seems like we could remove VMClass.getClassLoader altogether then
since it's public and static in VMStackWalker? On the other hand,
should it be public in VMStackWalker? Is that ok from a security
standpoint?
Stuart.
--
http://sab39.dev.netreach.com/
Jeroen Frijters wrote:
The infinite loop is simple:
Class.getClassLoader() invokes
VMStackWalker.getCallingClassLoader()
VMStackWalker.getCallingClassLoader() invokes
Class.getClassLoader()
It would be nice if VMStackWalker.getCallingClassLoader() could
invoke VMClass.getClassLoader(), b
Archie Cobbs wrote:
> I'm adapting JCVM to work with a totally unmodified Classpath, but
> doing so seems to cause an infinite loop in Mauve test
> gnu.testlet.java.util.logging.Logger.getAnonymousLogger.
>
> The infinite loop is simple:
>
>Class.getClassLoader() invokes
> VMStackWalker.getC
I'm adapting JCVM to work with a totally unmodified Classpath, but
doing so seems to cause an infinite loop in Mauve test
gnu.testlet.java.util.logging.Logger.getAnonymousLogger.
The infinite loop is simple:
Class.getClassLoader() invokes VMStackWalker.getCallingClassLoader()
VMStackWalker.g
--- Comment #25 from roman at kennke dot org 2005-11-09 15:30 ---
Subject: Re: JMenu layout problem with nested menus
Hi Norman,
Am Mittwoch, den 09.11.2005, 13:44 + schrieb hendrich at informatik
dot uni-hamburg dot de:
>
> --- Comment #24 from hendrich at informatik dot uni
Wow thats really impressive - I was a little bit sad when I last time
visited the Cacao site and saw that the last release was several
months ago but I didn't think about the fact that there were holidays
:-)
> A release is scheduled in 1-2 weeks and CACAO does not have anymore a
> own version of
The handling of newlines is broken. It should be treated as a character with
zero width. What the GTK peer do instead is return the maximum width of the
lines in the string. Run the attached testcase and you get the following with
the JDK:
[EMAIL PROTECTED]:~/src/test$ java TestRightAlignment
widt
On Tue, 2005-11-08 at 18:32 -0700, Tom Tromey wrote:
> > "Twisti" == Christian Thalinger <[EMAIL PROTECTED]> writes:
> Perhaps when it is ready we could integrate it into the build, so
> that errors here are unavoidable?
Uhm... that will be difficult since the tool is an enhancement of GCC.
It
On Tue, 2005-11-08 at 19:09 +0100, Mark Wielaard wrote:
> Yes, nice catch. Now that I have seen this I am surprised we don't have
> more bugs like this one. it is easy to miss. Cool to know you have a
> code analyzer for this. Please let us know when the paper is published.
We currently have only
11 matches
Mail list logo