A Java application how to pass AppVerifier?

[Crab Gu]

Hello,

I have a Java application that needs to pass OEM Ready program, but it fails
on AppVerifier. The error messages are:

"Freeing memory block inside current thread's stack address range."
"First chance access violation for current stack trace."

Anybody understands a Java application how to pass AppVerifier? Thanks in
advance.

p.s. The Java application is only a simple "Hello World" program.
p.s. I also test many popular Java applications (such as JBuilder), they
also cannot pass AppVerifier.

[Marc Sherman]

"Crab Gu" <Cra...@discussions.microsoft.com> wrote in message
news:0E718190-62F3-4130...@microsoft.com...

> Hello,
>
> I have a Java application that needs to pass OEM Ready program, but it
> fails
> on AppVerifier. The error messages are:
>
> "Freeing memory block inside current thread's stack address range."
> "First chance access violation for current stack trace."

I don't have an answer for you but I just wanted to add that we have a
native C++ app that loads the jvm.dll and runs some java code via JNI. When
we run it under the debugger, we see tons of first chance access violations
coming from the JVM but I guess it handles them all because there are no
second chance access violations.

Marc

[Neil Pike]

Crab - why would your Java application - presumably "just" a JAR file - need
to pass this? The verifier is for exectuables and you don't have an executable
file.

It's not your program that's "at fault", it's the JVM itself - presumably
either Sun's or IBM's. It's their issue to resolve, or not.

Neil Pike. Protech Computing Ltd
http://www.linkedin.com/in/neilpike

[Crab Gu]

Hi Neil,

Yes, you are right. But my customer asks this Java application need to pass
OEM Ready program.

I also think it should be Sun's JVM issue, but I need to give my customer a
rational reason to explain why our Java application cannot pass AppVerifier.

If you have any suggestion, help me please. Thanks.

[Neil Pike]

Crab,

You need to explain to the customer that this is a very "bad" test. Even if it
worked it wouldn't prove anything.

If they want to know your Java application doesn't leak resources then they should
ask you to run it under something like JProbe (Quest Software) that is designed to
check Java code.

The rational reason why AppVerifier can't be used is that AppVerifier isn't, in this
case, testing your code, it's testing the JVM's code - and there's nothing you can
do about the JVM's code, that's down to the folks that coded the JVM. i.e. Sun or
IBM.

> Yes, you are right. But my customer asks this Java application need to pass
> OEM Ready program.
>
> I also think it should be Sun's JVM issue, but I need to give my customer a
> rational reason to explain why our Java application cannot pass AppVerifier.
>
> If you have any suggestion, help me please. Thanks.

[Crab Gu]

Thanks for your suggestion.

> Crab,
>
> You need to explain to the customer that this is a very "bad" test. Even if it
> worked it wouldn't prove anything.
>
> If they want to know your Java application doesn't leak resources then they should
> ask you to run it under something like JProbe (Quest Software) that is designed to
> check Java code.
>
> The rational reason why AppVerifier can't be used is that AppVerifier isn't, in this
> case, testing your code, it's testing the JVM's code - and there's nothing you can
> do about the JVM's code, that's down to the folks that coded the JVM. i.e. Sun or
> IBM.
>