Re: [gnome-db]0.2.90 tarballs

[Vivien Malerba <malerba gnome-db org>]

On Wed, Aug 08, 2001 at 10:42:08AM +0200, Rodrigo Moya wrote:
> Hi Vivien!
> 
> First of all, sorry for the delay in answering
> 

You don't have to!

> > I have bonobo 1.0.7 installed as an RPM (prefix=/usr), and I always install Gnome-DB
> > from sources under prefix=/usr/local. This is the first time I have some problems.
> > I have solved to gnomedb-fe.xml problem by making a symlink from /usr/share/gnome/ui/gnomedb-fe.xml
> > to /usr/local/share/gnome/ui/gnomedb-fe.xml. Now there aren't anymore errors on startup
> > of gnomedb-fe. But it seems it can't find any component to display: I get an empty working
> > area. strange. If I try to load the connection manager from gASQL, it works
> >
> hmm, maybe it's because it can't find the XML files for the components. That is,
> all components have an associated XML file to describe their UI, so
> please try to also symlink those as you did with gnomedb-fe.xml
> 

I changed strategy and made RPMs for libgda and Gnome-DB and installed them, so they are 
in /usr now like the rest of the packages. I don't get any error message from gnomedb-fe
but it displays nothing. But from the Tools->Settings/Components, I see the Logs, Manager,
Designer and Database components and I can load and unload them!

What I discovered is that from gASQL I can get the manager, and that the manager also
crashes when I tried to test the connection (any connection). I think this is the same
bug as for gASQL.

Yesterday I tried to investigate starting from the gda-test program which works and I 
modified it to use gnome widgets and the gnome_db_init function. This one worked nicely!
I checked that the dynamic libraries in this case are the same as for gASQL!

Really I don't knwo where the problem can come from!

> >
> yes, strange. Seems something related to Bonobo.
>  

I agree but I don't know where to look (don't know enough bonobo). I think it is
related to the monikers.

> > > Can you make a more detailed debugging session? That is, add a
> > > breakpoint to gda_connection_open and run step by step there, to see
> > > where it's failing. And, when it fails, just get a backtrace (command bt
> > > in gdb) and send it to the list.
> > > 
> > 
> > Here is what this gives:
> > Message: Successfully registered `OAFIID:Bonobo_Moniker_std_Factory'
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x405eb9b3 in CORBA_Object_duplicate () from /usr/lib/libORBit.so.0
> > (gdb) bt
> > #0  0x405eb9b3 in CORBA_Object_duplicate () from /usr/lib/libORBit.so.0
> > #1  0x4065c0d1 in bonobo_moniker_util_qi_return () from /usr/lib/libbonobo.so.2
> > 
> > This morning, I've also had some strange crashes I don't really explain.
> > 
>  
> I don't recall any big fix getting into Bonobo CVS lately, but that may
> be the case. I'll try tonight to get those tarballs and make a clean
> compilation on a clean machine, to see if I can reproduce the errors you
> are getting.
> 
> Is there anybody else getting these crashes?
> 

Thanks for helping :)

Vivien

> cheers
> -- 
> Rodrigo Moya <rodrigo gnome-db org> - <rodrigo ximian com>
> http://www.gnome-db.org/ - http://www.ximian.com/
> 
> _______________________________________________
> gnome-db-list mailing list
> gnome-db-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-db-list