public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: Kurt Miller <kurt@intricatesoftware.com>
Cc: java@gcc.gnu.org
Subject: Re: gcj 4.6 on OpenBSD/x86
Date: Mon, 08 Oct 2012 20:35:00 -0000	[thread overview]
Message-ID: <50733907.9080108@gmail.com> (raw)
In-Reply-To: <201210081607.04804.kurt@intricatesoftware.com>

On 10/08/2012 01:07 PM, Kurt Miller wrote:
> Hi,
>
> Previously I ported gcj in gcc 4.2.4 to OpenBSD. I currently use it to build classpath-0.98 and bootstrap Oracle's 1.6 JVM using classpath and jamvm. I'm now working on gcj from gcc 4.6.3 on x86 and have run into an issue that I could use some help with.
>
> gjar is segfaulting while throwing a ClassCastException from frame 3. Here is some debugging output showing the state and some variables leading up to the segfault. I'm not sure where to go from here. I can't seem to find the root cause of this issue other than something is wrong with 'obj' in frame 3 and obj->getClass()->getName() fails. Any ideas on how to proceed with the debugging on this issue?
>
> Core was generated by `egjar'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x0c392970 in _Jv_NewStringUTF (bytes=0xfc408b05 <Address 0xfc408b05 out of bounds>)
>      at /usr/obj/i386/ports/gcc-4.6.3/gcc-4.6.3/libjava/java/lang/natString.cc:245
> 245       int size = strlen (bytes);
>
>

I haven't studied it closely, but it would appear that 'bytes=0xfc408b05 
<Address 0xfc408b05 out of bounds>' indicates a real problem.  If it is 
truly a bad pointer value, you need to figure out where it came from and 
fix it.

David Daney


  reply	other threads:[~2012-10-08 20:35 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 [this message]
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
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=50733907.9080108@gmail.com \
    --to=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).