Re: Fixed pgAdmin3 issues/asserts - Mailing list pgadmin-hackers

From Guillaume Lelarge
Subject Re: Fixed pgAdmin3 issues/asserts
Date
Msg-id 1330589934.2275.1.camel@localhost.localdomain
Whole thread Raw
In response to Re: Fixed pgAdmin3 issues/asserts  (Akshay Joshi <akshay.joshi@enterprisedb.com>)
List pgadmin-hackers
On Thu, 2012-03-01 at 13:44 +0530, Akshay Joshi wrote:
> Hi Guillaume
>
> On Thu, Mar 1, 2012 at 4:55 AM, Guillaume Lelarge
> <guillaume@lelarge.info> wrote:
>
>         On Tue, 2012-02-28 at 09:21 +0100, Guillaume Lelarge wrote:
>         > On Tue, 2012-02-28 at 12:41 +0530, Akshay Joshi wrote:
>         > > Hi Guillaume/Dave
>         > >
>         > > On Tue, Feb 28, 2012 at 4:02 AM, Guillaume Lelarge
>         > > <guillaume@lelarge.info> wrote:
>         > >         On Mon, 2012-02-27 at 16:49 +0000, Dave Page
>         wrote:
>         > >         > Thanks, applied.
>         > >         >
>         > >
>         > >         I probably have missed something. I thought the
>         work on 2.9
>         > >         wasn't
>         > >         finished. Are you able to compile with 2.9 on
>         Windows?
>         > >
>         > >
>         > >   Yes, I am able to compile it with 2.9 on Windows. I have
>         created two
>         > > configurations Debug (2.9) and Release(2.9) where
>         wxWidgets libraries
>         > > gets changed from
>         > >   2.8 to 2.9. Attached is the patch which contain changes
>         in ".sln"
>         > > and ".vcproj" file.
>         > >   For the work on 2.9 as concern, I have fixed
>         issues/asserts that I
>         > > have found. It is possible that there are many more such
>         > > asserts/issues that we will have to fix.
>         > >
>         > >   Dave, If patch looks good to you then can you please
>         commit it.
>         > >
>         >
>         > That's great. If your .sln/.vcproj files allow us to still
>         work on 2.8,
>         > I see no reason not to apply them. (I won't apply them
>         myself because I
>         > have no Windows PC right now to check them, but I guess Dave
>         will be
>         > able to do that quicker than me)
>         >
>
>
>         I compiled 2.9 on my laptop, and compiled pgAdmin master
>         against it.
>         Compilation went fine, but I cannot start it. Did you also
>         build it on
>         Linux? and if so, does it work for you?
>
>
>    I am facing the same issue on my Ubuntu machine. I got segmentation
> fault with below mentioned error messages
>
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-CRITICAL **: g_once_init_leave: assertion
> `initialization_value != 0' failed
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL **: g_type_add_interface_static:
> assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL **: g_type_add_interface_static:
> assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL **: g_type_add_interface_static:
> assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-CRITICAL **: g_once_init_leave: assertion
> `initialization_value != 0' failed
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL
> **: /build/buildd/glib2.0-2.24.1/gobject/gtype.c:2706: You forgot to
> call g_type_init()
> (process:3401): GLib-GObject-CRITICAL **: g_type_add_interface_static:
> assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
> (process:3401): GLib-CRITICAL **: g_once_init_leave: assertion
> `initialization_value != 0' failed
> (process:3401): GLib-GObject-CRITICAL **: g_object_new: assertion
> `G_TYPE_IS_OBJECT (object_type)' failed
> Segmentation fault
>
>
>  I have googled but unable to find any solution. Will working on the
> same.
>

I have the same messages, but not the segmentation fault. It just seems
to freeze. Maybe I didn't wait enough to get the segfault.

Thanks for looking into it.


--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com


pgadmin-hackers by date:

Previous
From: Akshay Joshi
Date:
Subject: Re: Fixed pgAdmin3 issues/asserts
Next
From: Dave Page
Date:
Subject: Re: Fixed pgAdmin3 issues/asserts