public inbox for
 help / color / mirror / Atom feed
From: "Johann 'Myrkraverk' Oskarsson" <>
To: GCC Java <>
Subject: Re: Garbage collection segfault in OpenIndiana
Date: Sun, 13 Nov 2011 23:25:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Andrew Haley's message of "Sun, 13 Nov 2011 16:35:17 +0000")

Andrew Haley <> writes:

> On 11/12/2011 08:38 PM, Johann 'Myrkraverk' Oskarsson wrote:
>> With GCC 4.6.2 on OpenIndiana 151a (Solaris) the boehm gc segfaults
>> in os_dep.c:810 when JNI_CreateJavaVM() is called.
>> I thought of merging boehm gc 7.1 into the gcc source tree, but
>> this seems non-trivial.  In particular it's not possible just to
>> make it a drop-in replacement.
> Do you have any reason to suspect that merging gc 7.1 might help?

No concrete evidence.  In the past I was unable to use 6.x on it while
7.x worked in my own projects.  In 7.1 and 7.2alpha6 this function is
now called GC_find_limit_with_bound() instead of just GC_find_limit().
The relevant line number in 7.2alpha6 is os_dep.c:994.

I suppose the best way to be sure is to compare the output of gcc -E
for os_dep.c.

If you have any further ideas I can explore, please let me know.

   Johann Oskarsson          |[]
   PostgreSQL Development, 24x7 Support, Training and Services  --+--

  reply	other threads:[~2011-11-13 23:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-14  3:41 gcj onLinux, 32 and 64 bit executables Me Myself and I
2011-09-14  7:50 ` Jonathan Wakely
2011-11-13 16:35 ` Andrew Haley
2011-11-13 23:25   ` Johann 'Myrkraverk' Oskarsson [this message]
2011-11-12 20:38 Garbage collection segfault in OpenIndiana Johann 'Myrkraverk' Oskarsson

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