markers dropdowns
Hi guys, Looking at the logs from the chatroom, it seems the marker selection dropdowns are crashing inkscape on you guys? I knew the previews didnt work (which is why i disabled them) but I didnt realise the menus themselves were killing the prog. Is it giving any messages? They work fine for me here on windows, so I'm not sure whats going on. (or how to go about fixing a problem on a platform i dont have access to.)
some feedback would be appreciated.
Cheers
John
__________________________________ Do you Yahoo!? Yahoo! Tax Center - File online by April 15th http://taxes.yahoo.com/filing.html
Yes they are crashing it. It returns a generic error message and iirc it doesn't print anything to the commandline.
Bryce
On Thu, 15 Apr 2004, John Cliff wrote:
Hi guys, Looking at the logs from the chatroom, it seems the marker selection dropdowns are crashing inkscape on you guys? I knew the previews didnt work (which is why i disabled them) but I didnt realise the menus themselves were killing the prog. Is it giving any messages? They work fine for me here on windows, so I'm not sure whats going on. (or how to go about fixing a problem on a platform i dont have access to.)
some feedback would be appreciated.
Cheers
John
__________________________________ Do you Yahoo!? Yahoo! Tax Center - File online by April 15th http://taxes.yahoo.com/filing.html
This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, Apr 15, 2004 at 11:08:53AM -0700, John Cliff wrote:
(which is why i disabled them) but I didnt realise the menus themselves were killing the prog. Is it giving any messages? They work fine for me here on windows, so I'm not sure whats going on. (or how to go about fixing a problem on a platform i dont have access to.)
gdb says it's from a crashed "free" which means there is probably a double-free going on, after I select any item from the drop-down. The backtrace:
#0 0x40842a8b in free () from /lib/tls/libc.so.6 #1 0x0823c950 in sp_display_dialog_set_oversample(_GtkMenuItem*, void*)::__PRETTY_FUNCTION__ () #2 0x40398379 in g_value_peek_pointer () from /usr/lib/libgobject-2.0.so.0 #3 0x4038f212 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #4 0x4037ea92 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #5 0x4038eda6 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #6 0x4038dec2 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #7 0x4038e0d6 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #8 0x4011c265 in gtk_option_menu_get_history () from /usr/lib/libgtk-x11-2.0.so.0 #9 0x4011c478 in gtk_option_menu_get_history () from /usr/lib/libgtk-x11-2.0.so.0 #10 0x4038f212 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #11 0x4037ea92 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #12 0x4038ec6d in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #13 0x4038dec2 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #14 0x4038e0d6 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #15 0x4010c1da in gtk_menu_shell_activate_item () from /usr/lib/libgtk-x11-2.0.so.0 #16 0x4010b4a7 in _gtk_menu_shell_activate () from /usr/lib/libgtk-x11-2.0.so.0 #17 0x40104b66 in gtk_menu_reorder_child () from /usr/lib/libgtk-x11-2.0.so.0 #18 0x400fc9e4 in _gtk_marshal_BOOLEAN__BOXED () from /usr/lib/libgtk-x11-2.0.so.0 #19 0x4037ed44 in g_cclosure_new_swap () from /usr/lib/libgobject-2.0.so.0 #20 0x4037ea92 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #21 0x4038e895 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #22 0x4038dca3 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #23 0x4038e0d6 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #24 0x401deca7 in gtk_widget_send_expose () from /usr/lib/libgtk-x11-2.0.so.0 #25 0x400fc7a7 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0 #26 0x400fb506 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 #27 0x402b8845 in _gdk_events_queue () from /usr/lib/libgdk-x11-2.0.so.0 #28 0x403ce086 in unblock_source () from /usr/lib/libglib-2.0.so.0 #29 0x403cf029 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #30 0x403cf347 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #31 0x403cf9b0 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #32 0x400fad2f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
Kees Cook wrote:
gdb says it's from a crashed "free" which means there is probably a double-free going on, after I select any item from the drop-down. The backtrace:
From what I've seen, with gcc and glibc code, a crash on a free() or a malloc() is often the result of code writing out-of-bounds on a previously-allocated memory chunk, thus destroying the nice linked-list heap structure of the allocatable memory upon which malloc() operates. So you might want to check what the last code that used allocated memory was doing.
It is likely something else, but that is what I have often seen.
Bob
participants (4)
-
Bob Jamison -
Bryce Harrington -
John Cliff -
Kees Cook