public inbox for
 help / color / mirror / Atom feed
From: David Daney <>
To: majia gm <>
Cc: Java List <>,
Subject: Re: Must unwind in gcc be ported for gcj?
Date: Thu, 24 Feb 2011 02:34:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 02/23/2011 05:19 PM, majia gm wrote:
> Hi, everyone.
> I'm porting gcj (gcc-4.4.2) to another platform. Right now the gij
> fails when interpreting the following program.
> File
> import B;
> public class A{
> 	public static void main(String args[])
> 	{
> 		try{
> 			B b=(B)Class.forName("B").newInstance();
> 		catch(Exception e)
> 		{
> 			System.out.println("Cannot find Class B");
> 		}
> 	}
> }
> File
> public class B
> {}
> I use gdb to track gij, and I found GetCallingClass() in forName()
> returns NULL, then the bootstrap loader is used to search the Class B
> but with no result. Should the Class B has the same class loader, the
> system class loader as the Class A dose?
> Then I track the GetCallingClass(), and I found it needs the unwind
> function provided by gcc.  Must I port the unwind function?

Short answer: Yes.

libgcj relies internally on exception handling.

You might be able to construct simple programs that don't throw 
exceptions, but they are kind of a core language feature.

As you saw, the runtime startup code does throw and catch exceptions.

David Daney

  reply	other threads:[~2011-02-24  2:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24  1:19 majia gm
2011-02-24  2:34 ` David Daney [this message]
2011-02-24 10:07 ` Bryce McKinlay

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).