Re: ** ERROR **: sigsegv caught



I ran the help-browser and same-gnome with xxgdb and got the following
stack trace (in case no-one else has yet...)

The following for same-gnome...
(xxgdb) info stack
#0  0x4036cd43 in memcpy (dstpp=0x807fb00, srcpp=0x8146208, len=6) at
../sysdeps/generic/memcpy.c:57
#1  0x40286d11 in NoSwap ()
#2  0x40287af4 in SendXYImage ()
#3  0x40287e7b in PutImageRequest ()
#4  0x40287f7a in PutSubImage ()
#5  0x402882fb in XPutImage ()
#6  0x400aa190 in gdk_imlib_render ()
#7  0x40046d9b in finish_load (gpixmap=0x807ec30, im=0x807ec70,
scaled=0, width=0, height=0, destroy=1) at gnome-pixmap.c:449
#8  0x40046fc0 in load_rgb_d_shaped (gpixmap=0x807ec30, data=0x807e808
"ÿ", alpha=0x0, rgb_width=16, rgb_height=16, scaled=0, width=0,
height=0, shape_color=0x4008a0f0) at gnome-pixmap.c:519
#9  0x40047489 in gnome_pixmap_load_rgb_d_shaped (gpixmap=0x807ec30,
data=0x807e808 "ÿ", alpha=0x0, rgb_width=16, rgb_height=16,
shape_color=0x4008a0f0) at gnome-pixmap.c:591
#10 0x40046359 in gnome_pixmap_new_from_rgb_d_shaped (data=0x807e808
"ÿ", alpha=0x0, rgb_width=16, rgb_height=16, shape_color=0x4008a0f0) at
gnome-pixmap.c:193
#11 0x4004aa90 in create_pixmap_from_imlib_scaled (window=0x807e4a0,
data=0x807cf70) at gnome-stock.c:650
#12 0x4004aef9 in gnome_stock_pixmap (window=0x807e4a0, icon=0x807e7f8
"Menu_New", subtype=0x4006c104 "regular") at gnome-stock.c:777
#13 0x40049fb8 in gnome_stock_pixmap_widget_state_changed
(widget=0x807e790, prev_state=0) at gnome-stock.c:141
#14 0x4004a360 in gnome_stock_pixmap_widget_new (window=0x807e4a0,
icon=0x804bebe "Menu_New") at gnome-stock.c:253
#15 0x4004af9f in gnome_stock_pixmap_widget (window=0x807e4a0,
icon=0x804bebe "Menu_New") at gnome-stock.c:802
#16 0x4004b69e in gnome_stock_menu_item (type=0x804bebe "Menu_New",
text=0x804bec7 "New") at gnome-stock.c:1007
#17 0x400286a5 in gnome_app_do_menu_creation (app=0x8079570,
parent_widget=0x807b9a0, pos=0, menuinfo=0x804d08c, uidata=0xbffffa6c)
at gnome-app-helper.c:143
#18 0x40028894 in gnome_app_do_menu_creation (app=0x8079570,
parent_widget=0x807a300, pos=1, menuinfo=0x804d1ec, uidata=0xbffffa6c)
at gnome-app-helper.c:193
#19 0x40028d78 in gnome_app_create_menus_custom (app=0x8079570,
menuinfo=0x804d1ec, uibdata=0xbffffa6c) at gnome-app-helper.c:349
#20 0x40028e57 in gnome_app_create_menus (app=0x8079570,
menuinfo=0x804d1ec) at gnome-app-helper.c:370
#21 0x804ba76 in main (argc=1, argv=0xbffffab0) at same-gnome.c:913

With the gnome-help-browser, the following were different (besides
actaul addresses):
#20 0x40028ea9 in gnome_app_create_menus_with_data (app=0x80fd158,
menuinfo=0x8056400, data=0x80fcf98) at gnome-app-helper.c:383
#21 0x8051ccc in helpWindowNew (name=0x8053412 "GnomeHelp", x=0, y=0,
width=0, height=0, about_callback=0x804c46c <aboutCallback>,
new_window_callback=0x804c3e0 <newWindowCallback>,
close_window_callback=0x804c3b0 <closeWindowCallback>,
set_current_callback=0x804c384 <setCurrentCallback>,
config_callback=0x804ccdc <configCallback>) at window.c:696
#22 0x804c21f in makeHelpWindow (x=0, y=0, w=0, h=0) at
gnome-help-browser.c:218
#23 0x804c182 in main (argc=1, argv=0xbffffaa0) at
gnome-help-browser.c:192

In both cases, it (obviously) is in the menu code.  Running
gnome-session also gets a seg fault trap, but not serious enough to quit
the program - no menus!  Don't ask why it doesn't quit - I don't know.

These sources are from the CVS tree today. (Monday morning, 10 Aug)

--Jim Smith



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