Hi all,
I'm trying to compile the latest inkscape CVS and so I have update some libs : glibmm (to 2.4.3) , gtkmm (to 2.4.4) and libsigc++ (to 2.0.2) on my Linux system.
There was no problem with "./configure" or "make" but impossible to launch Inkscape :( I've got the message "Inkscape encountered an internal error and will close now." immediatly at the startup.
Does anyone have an idea ?
FlorentGabriel
Yes, I had the same problem, I was debugging the problem and I found new functions that must be related to adding layers, as a matter of fact if you comment some of these functions you will put it to work, but is completely worthless it still is useless because it crashes when you do any action. Probably the best think is to wait a little bit. ROberto
Hi all,
I'm trying to compile the latest inkscape CVS and so I have update some libs : glibmm (to 2.4.3) , gtkmm (to 2.4.4) and libsigc++ (to 2.0.2) on my Linux system.
There was no problem with "./configure" or "make" but impossible to launch Inkscape :( I've got the message "Inkscape encountered an internal error and will close now." immediatly at the startup.
Does anyone have an idea ?
FlorentGabriel
This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
glibmm (to 2.4.3) , gtkmm (to 2.4.4) and libsigc++ (to 2.0.2) on my Linux system.
There was no problem with "./configure" or "make" but impossible to launch Inkscape :( I've got the message "Inkscape encountered an internal error and will close now." immediatly at the startup.
any action. Probably the best think is to wait a little bit.
But maybe, the problem come from the new libs version ? Is there anyone who can run the last CVS on a Linux ? And what is his lib versions ?
I don't know if it can help but when I run the "ddd inkscape", it gives me :
Program received signal SIGSEGV, Segmentation fault. SPDesktop::_layer_hierarchy_changed(SPObject*, SPObject*, SPDesktop*) (top=0x84023d0, bottom=0x84023d0, desktop=0x86bc208) at stl_list.h:397 /usr/include/c++/3.2.3/bits/stl_list.h:397:10573:beg:0x815f4c4
FlorentGabriel
Apparently we are facing the same problem. Is anybody else in this community trying to compile the new CVS and having the same problem? In my case, I couldn't compile the CVS anymore after the latest 0.39 release.
Roberto.
Program received signal SIGSEGV, Segmentation fault. SPDesktop::_layer_hierarchy_changed(SPObject*, SPObject*, SPDesktop*) (top=0x84023d0, bottom=0x84023d0, desktop=0x86bc208) at stl_list.h:397 /usr/include/c++/3.2.3/bits/stl_list.h:397:10573:beg:0x815f4c4
Sorry for taking so long to get back to you; emails about compilation problems will probably get answered quicker on the development mailing list...
On Thu, 2004-07-22 at 16:05, Florent wrote:
But maybe, the problem come from the new libs version ? Is there anyone who can run the last CVS on a Linux ?
Yes, I've been running it since I did the library conversion.
And what is his lib versions ?
gtk+-2.0 = 2.4.3 gobject-2.0 = 2.4.2 gmodule-2.0 = 2.4.2 glib-2.0 = 2.4.2 pango = 1.4.0
gtkmm-2.4 = 2.4.4 gdkmm-2.4 = 2.4.4 glibmm-2.4 = 2.4.3 pangomm-1.4 = 2.4.4
I don't know if it can help but when I run the "ddd inkscape", it gives me :
Program received signal SIGSEGV, Segmentation fault. SPDesktop::_layer_hierarchy_changed(SPObject*, SPObject*, SPDesktop*) (top=0x84023d0, bottom=0x84023d0, desktop=0x86bc208) at stl_list.h:397 /usr/include/c++/3.2.3/bits/stl_list.h:397:10573:beg:0x815f4c4
void SPDesktop::_layer_hierarchy_changed(SPObject *top, SPObject *bottom, SPDesktop *desktop) { desktop->_layer_changed_signal.emit(bottom); }
That place for the crash looks a little strange to me. Could you try compiling without optimization and see if it yields the same backtrace (and give me some more of the actual backtrace as well..).
The only reason I can think of that it would crash here is if SPDesktop::_layer_changed_signal were not initialized properly for some reason.
-mental
I am afraid I didnt success. These are my librairies:
gtk+-2.0: 2.4.3 gobject-2.0: 2.4.4 gmodule-2.0: 2.4.4 pango: 1.4.0 gtkmm-2.4: 2.4.3 glibmm-2.4: 2.4.3 pangomm-1.4: 2.4.3 sigc++-2.0: 2.0.2
After I took out the optimization flag I got a diferent error in the dbg:
glib-2.0: 2.4.4Program received signal SIGSEGV, Segmentation fault. sigc::internal::signal_emit1<void, SPObject*,
sigc::nil>::emit(sigc::internal::signal_impl*, >SPObject* const&) (impl=0x0, _A_a1=@0xbfffe8b4)
at /usr/include/g++/bits/stl_list.h:628 628 empty() const { return _M_node->_M_next == _M_node; }
I am using gcc 3.3.1 in a SUSE 8.2 linux with libc 2.3.2 runining under KDE.
Roberto.
Sorry for taking so long to get back to you; emails about compilation problems will probably get answered quicker on the development mailing list...
On Thu, 2004-07-22 at 16:05, Florent wrote:
But maybe, the problem come from the new libs version ? Is there anyone who can run the last CVS on a Linux ?
Yes, I've been running it since I did the library conversion.
And what is his lib versions ?
gtk+-2.0 = 2.4.3 gobject-2.0 = 2.4.2 gmodule-2.0 = 2.4.2 glib-2.0 = 2.4.2 pango = 1.4.0
gtkmm-2.4 = 2.4.4 gdkmm-2.4 = 2.4.4 glibmm-2.4 = 2.4.3 pangomm-1.4 = 2.4.4
I don't know if it can help but when I run the "ddd inkscape", it gives me :
Program received signal SIGSEGV, Segmentation fault. SPDesktop::_layer_hierarchy_changed(SPObject*, SPObject*, SPDesktop*) (top=0x84023d0, bottom=0x84023d0, desktop=0x86bc208) at stl_list.h:397 /usr/include/c++/3.2.3/bits/stl_list.h:397:10573:beg:0x815f4c4
void SPDesktop::_layer_hierarchy_changed(SPObject *top, SPObject *bottom, SPDesktop *desktop) { desktop->_layer_changed_signal.emit(bottom); }
That place for the crash looks a little strange to me. Could you try compiling without optimization and see if it yields the same backtrace (and give me some more of the actual backtrace as well..).
The only reason I can think of that it would crash here is if SPDesktop::_layer_changed_signal were not initialized properly for some reason.
-mental
participants (3)
-
Florent -
MenTaLguY -
Roberto Ortega