public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Boehm, Hans" <hans.boehm@hp.com>
To: Kurt Miller <kurt@intricatesoftware.com>, Andrew Haley <aph@redhat.com>
Cc: David Daney <ddaney.cavm@gmail.com>,
	"java@gcc.gnu.org" <java@gcc.gnu.org>
Subject: RE: gcj 4.6 on OpenBSD/x86
Date: Tue, 09 Oct 2012 17:22:00 -0000	[thread overview]
Message-ID: <A3E67C2071F49C4CBC4F17E6D77CDDD235F8B32F@G4W3296.americas.hpqcorp.net> (raw)
In-Reply-To: <50742135.3000000@intricatesoftware.com>

It may be worth checking whether the garbage collector tests, particularly gctest, run correctly in your environment.  If not, that might give you an easier debugging task.

Hans

> -----Original Message-----
> From: java-owner@gcc.gnu.org [mailto:java-owner@gcc.gnu.org] On Behalf
> Of Kurt Miller
> Sent: Tuesday, October 09, 2012 6:06 AM
> To: Andrew Haley
> Cc: David Daney; java@gcc.gnu.org
> Subject: Re: gcj 4.6 on OpenBSD/x86
> 
> On 10/8/12 8:51 PM, Andrew Haley wrote:
> > On 10/08/2012 03:09 PM, Kurt Miller wrote:
> >> Indeed. I've done that already and included the details in the
> initial email.
> >> Frame 3 is throwing an exception where obj->getClass()->getName() is
> >> called. 'obj' is the likely source of the problem but the debugger
> believes it is
> >> an incomplete type and I can't inspect it; see the end of initial
> email.
> > I'd put a breakpoint earlier and step through.
> > I don't think there's an easier way to do it.
> >
> > _Jv_Debug(obj) prints an object.
> >
> > Andrew.
> >
> 
> Thanks. It looks like the root of the problem lies in boehm-gc. Using
> GC_DONT_GC=1 works-around the problem. Time to dig into boehm-gc ifdef
> hell again...
> 
> -Kurt

  reply	other threads:[~2012-10-09 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 20:08 Kurt Miller
2012-10-08 20:35 ` David Daney
2012-10-08 22:10   ` Kurt Miller
2012-10-09  0:51     ` Andrew Haley
2012-10-09 13:06       ` Kurt Miller
2012-10-09 17:22         ` Boehm, Hans [this message]
2012-10-09 18:27           ` Kurt Miller
2012-10-10 13:33           ` Kurt Miller
2012-10-14 11:26             ` Kurt Miller

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=A3E67C2071F49C4CBC4F17E6D77CDDD235F8B32F@G4W3296.americas.hpqcorp.net \
    --to=hans.boehm@hp.com \
    --cc=aph@redhat.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=java@gcc.gnu.org \
    --cc=kurt@intricatesoftware.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).