From: Mark Wielaard <mark@klomp.org>
To: tromey@redhat.com
Cc: mauve-discuss@sourceware.org,
Nicolas Geoffray <nicolas.geoffray@menlina.com>,
classpath@gnu.org
Subject: Re: Wrong exception thrown in AccessContoller
Date: Wed, 05 Oct 2005 21:11:00 -0000 [thread overview]
Message-ID: <1128546663.12848.47.camel@localhost.localdomain> (raw)
In-Reply-To: <m3vf0zbssk.fsf@localhost.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 518 bytes --]
Hi,
On Sat, 2005-09-17 at 09:47 -0600, Tom Tromey wrote:
> >>>>> "Nicolas" == Nicolas Geoffray <nicolas.geoffray@menlina.com> writes:
>
> Nicolas> I attached a patch (it's patched against 0.13, but it's ok for 0.18)
> Nicolas> and a java program which execution is different between sun and gnu
> Nicolas> classpath.
>
> Could you turn this into a Mauve test?
I created the attached Mauve test for it. And tested that without the
patch we have one failure, with the patch all pass.
Cheers,
Mark
[-- Attachment #1.2: doPrivileged.java --]
[-- Type: text/x-java, Size: 2371 bytes --]
// Copyright (C) 2005, Free Software Foundation, Inc.
//
// This file is part of Mauve.
//
// Mauve is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License as published by
// the Free Software Foundation; either version 2, or (at your option)
// any later version.
//
// Mauve is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with Mauve; see the file COPYING. If not, write to
// the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
// Boston, MA, 02110-1301 USA.
//
// Tags: JDK1.2
package gnu.testlet.java.security.AccessController;
import gnu.testlet.Testlet;
import gnu.testlet.TestHarness;
import java.security.*;
/**
* Checks that unchecked exceptions are properly thrown and checked
* exceptions are properly wrapped.
*
* Written by Mark J. Wielaard. Suggested by Nicolas Geoffray.
*/
public class doPrivileged implements Testlet, PrivilegedExceptionAction
{
// The thing to throw.
private Throwable t;
public void test(TestHarness harness)
{
doPrivileged pea = new doPrivileged();
pea.t = new NullPointerException();
try
{
AccessController.doPrivileged(pea);
}
catch (NullPointerException npe)
{
harness.check(true);
}
catch (Throwable tt)
{
harness.debug(tt);
harness.check(false);
}
pea.t = new java.io.IOException();
try
{
AccessController.doPrivileged(pea);
}
catch (PrivilegedActionException pae)
{
harness.check(pea.t, pae.getCause());
}
catch (Throwable tt)
{
harness.debug(tt);
harness.check(false);
}
pea.t = new ThreadDeath();
try
{
AccessController.doPrivileged(pea);
}
catch (ThreadDeath td)
{
harness.check(true);
}
catch (Throwable tt)
{
harness.debug(tt);
harness.check(false);
}
}
public Object run() throws Exception
{
if (t instanceof Error)
throw (Error) t;
else
throw (Exception) t;
}
}
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
parent reply other threads:[~2005-10-05 21:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m3vf0zbssk.fsf@localhost.localdomain>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1128546663.12848.47.camel@localhost.localdomain \
--to=mark@klomp.org \
--cc=classpath@gnu.org \
--cc=mauve-discuss@sourceware.org \
--cc=nicolas.geoffray@menlina.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).