Re: SIGSEGV caused by libgconf-2.so.4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Il giorno ven, 04/08/2006 alle 10.13 +1000, Raif S. Naffah ha scritto:
> On Friday 04 August 2006 09:49, Raif S. Naffah wrote:
> > On Friday 04 August 2006 09:32, Mario Torre wrote:
> > > Il giorno ven, 04/08/2006 alle 09.12 +1000, Raif S. Naffah ha scritto:
> > > > i'm getting a segmentation fault caused by /usr/lib/libgconf-2.so.4
> > > > (FC5) when trying to run jamvm with Classpath (both CVS Head)...
> > > > anybody else is seeing this?
> > >
> > > Do you have a test case for that?
> >
> > here is how i can trigger it:
> >
> > import java.util.prefs.Preferences;
> >
> > public class Hello {
> >   public static final void main(String[] args) {
> >     Preferences prefs = Preferences.systemNodeForPackage(Hello.class);
> >     int lastSerialNumber = prefs.getInt("LAST_SERIAL_NUMBER", 0) + 1;
> >     prefs.putInt("LAST_SERIAL_NUMBER", lastSerialNumber);
> >   }
> > }

I can't reproduce.

Moreover, you get a warning if you put this into the default package (it
does not cause harm), but other than that, it is fine (the warning is
normal).

Anyway, Can you try the attached patch and see if it works?

> in addition to the above, when i configure Classpath with
> --disable-default-preferences-peer, and try to run the same code (as
> above) i get:

Well, sorry this is my fault, I hope to fix this tomorrow, as I'm not an
autoconf expert, so I have to look at it in more details (and now I
really need some sleep).

There should not be any --disable-default-preferences-peer.

The preference flags are intended to use this way:

--disable-gconf-peer: disable the gconf backend
--enable-default-preferences-peer=gnu.java.util.prefs.FileBasedFactory:
use another backend, not the default (everything that this default is,
may also not be gconf).

This means that you can build the preference backend but with another
default, or you can totally disable the preference backend.

I guess that --disable-default-preferences-peer should not create any
key in the META-INF directory.

The correct name for this flag should really be
--with-default-preferences-peer...

The exceptions are normal, it should revert to a sane default if
everything else fails. This should be the FileBasedPreferences, can you
please confirm this? What happened after the error?

Sorry for the confusion, and thanks for pointing me out to this
Mario
-- 
Lima Software, SO.PR.IND. s.r.l.
http://www.limasoftware.net/
pgp key: http://subkeys.pgp.net/

Please, support open standards:
http://opendocumentfellowship.org/petition/
http://www.nosoftwarepatents.com/
### Eclipse Workspace Patch 1.0
#P classpath
Index: native/jni/gconf-peer/GConfNativePeer.c
===================================================================
RCS file: /sources/classpath/classpath/native/jni/gconf-peer/GConfNativePeer.c,v
retrieving revision 1.6
diff -u -r1.6 GConfNativePeer.c
--- native/jni/gconf-peer/GConfNativePeer.c	15 Jul 2006 22:59:23 -0000	1.6
+++ native/jni/gconf-peer/GConfNativePeer.c	4 Aug 2006 00:45:56 -0000
@@ -551,8 +551,8 @@
 
 static void init_gconf_client (void)
 {
-  client = gconf_client_get_default ();
   g_type_init ();
+  client = gconf_client_get_default ();
 }
 
 static gboolean set_jlist_class (JNIEnv *env)

Attachment: signature.asc
Description: Questa =?ISO-8859-1?Q?=E8?= una parte del messaggio firmata digitalmente


[Index of Archives]     [Linux Kernel]     [Linux Cryptography]     [Fedora]     [Fedora Directory]     [Red Hat Development]

  Powered by Linux