Bug#148385: marked as done (JNI/C++ Exceptions using glib2.1 and Sun JVM)
Your message dated Tue, 20 May 2003 23:21:09 +0200
with message-id <16074.40005.875790.800405@gargle.gargle.HOWL>
and subject line JNI/C++ Exceptions using glib2.1 and Sun JVM
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 28 May 2002 15:31:27 +0000
>From sclarke@ideorlando.org Tue May 28 10:31:27 2002
Return-path: <sclarke@ideorlando.org>
Received: from (mail.ideorlando.org) [208.63.70.76] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17CiwY-0000tU-00; Tue, 28 May 2002 10:31:26 -0500
Received: from sclarkel (unknown [192.168.10.1])
by mail.ideorlando.org (Postfix) with ESMTP id 81CCB36AD5
for <submit@bugs.debian.org>; Tue, 28 May 2002 11:21:59 -0400 (EDT)
Subject: JNI/C++ Exceptions using glib2.1 and Sun JVM
From: Scott Clarke <sclarke@ideorlando.org>
To: submit@bugs.debian.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/1.0.2
Date: 28 May 2002 11:28:48 -0400
Message-Id: <1022599728.5084.97.camel@sclarkel>
Mime-Version: 1.0
Delivered-To: submit@bugs.debian.org
Package: libstdc++2.9-glibc2.1
Version: 2.91.66-4
There appears to be an incompatibility between the Sun JVM and the
Debian Linux version of glibc2.1 that causes all C++ exceptions to
result in a Segmentation Fault.
I think I narrowed the problem down to
/usr/lib/libstdc++-libc6.1-1.so.2. If I symbolically link to
/usr/lib/libstdc++-libc6.2-2.so.3 (using the former name) in my
LD_LIBRARY_PATH, everything works fine.
BTW, everything works fine under Redhat 7.2, and everything works fine
using Blackdown JVM, but not when using Sun JVM and Debian together.
Not sure if this is a Debian glibc problem, or if this is a Sun JVM
problem.
---------------------------------------
Received: (at 148385-done) by bugs.debian.org; 20 May 2003 21:26:29 +0000
>From doko@cs.tu-berlin.de Tue May 20 16:25:55 2003
Return-path: <doko@cs.tu-berlin.de>
Received: from mail.cs.tu-berlin.de [130.149.17.13]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 19IEcJ-0002bN-00; Tue, 20 May 2003 16:25:51 -0500
Received: from bolero.cs.tu-berlin.de (daemon@bolero.cs.tu-berlin.de [130.149.19.1])
by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id XAA14541
for <148385-done@bugs.debian.org>; Tue, 20 May 2003 23:21:10 +0200 (MET DST)
Received: (from doko@localhost)
by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id h4KLLAH07800;
Tue, 20 May 2003 23:21:10 +0200 (MEST)
From: Matthias Klose <doko@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16074.40005.875790.800405@gargle.gargle.HOWL>
Date: Tue, 20 May 2003 23:21:09 +0200
To: 148385-done@bugs.debian.org
Subject: Re: JNI/C++ Exceptions using glib2.1 and Sun JVM
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
Delivered-To: 148385-done@bugs.debian.org
X-Spam-Status: No, hits=-8.9 required=4.0
tests=QUOTED_EMAIL_TEXT,USER_AGENT_VM
version=2.53-bugs.debian.org_2003_05_09
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_09 (1.174.2.15-2003-03-30-exp)
Debian potato uses glibc-2.1 (libstdc++2.9-glibc2.1). Looking at the
soname I assume the JVM was built on a glibc-2.2 based system. Adding
the symlink is known to work in some cases, don't know if this is the
case for the Sun JVM. Anyway, as our last released Debian version is
woody, I'm closing this report.
> There appears to be an incompatibility between the Sun JVM and the
> Debian Linux version of glibc2.1 that causes all C++ exceptions to
> result in a Segmentation Fault.
>
> I think I narrowed the problem down to
> /usr/lib/libstdc++-libc6.1-1.so.2. If I symbolically link to
> /usr/lib/libstdc++-libc6.2-2.so.3 (using the former name) in my
> LD_LIBRARY_PATH, everything works fine.
>
> BTW, everything works fine under Redhat 7.2, and everything works fine
> using Blackdown JVM, but not when using Sun JVM and Debian together.
>
> Not sure if this is a Debian glibc problem, or if this is a Sun JVM
> problem.
Reply to: