gtk2 dies on Tiger/1.6.0 but works on Tiger/1.7.0

[north@…]

I hesitate to mention this but it might be useful. Three different attempts at building gtk2 on Tiger/Developer2.5 with macports 1.6.0 yielded a binary that would not run gtk apps; it simply reported "Bus Error" and died gracefully.

The interesting thing is I downloaded the 1.7.0 Beta 1 source and the resultant gtk2 runs gtk apps fine on the same setup. Thumbs up for 1.7.0 so far.

(Failed 1.6.0 attempts were "with a bunch of other stuff already in place," cleaning out ports and starting again building only gtk2 and its dependencies, and then building each dependency first to avoid complications caused by perl5 and perl5.8 colliding).

[jmroot (Joshua Root)]

gtk2 built with 1.6.0 seems fine here. More information is needed to determine if there's actually something useful that can be done here.

[north@…]

Some additional info:

First, I fished through the comparative setups and some strange orientation of the planets and files left in the directory meant when 1.7.0 built xrender, it did not pull in all the xorg-libX11 cruft; just xorg-renderproto. With that as a clue, I ran gdb on a little gtk app. Here's the output:

(gdb) run pix/backgrounds/*.jpg Starting program: /Users/d/bin/pho pix/backgrounds/*.jpg Reading symbols for shared libraries .................................................................++++++...+.++...+++++....+++++.............+..+++ done

Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000008 0x0178d8c8 in _XSend () (gdb) Quit (gdb) where #0 0x0178d8c8 in _XSend () #1 0x01779624 in XQueryExtension () #2 0x0176c8f8 in XInitExtension () #3 0x000f9a58 in XRenderFindDisplay () #4 0x000f9c2c in XRenderQueryExtension () #5 0x002c8404 in _gdk_x11_have_render () #6 0x002f1a68 in _gdk_x11_get_xft_setting () #7 0x002ceda0 in gdk_screen_get_setting () #8 0x01161e18 in gtk_settings_get_property () #9 0x0074b074 in g_object_get_valist () #10 0x0074b2c8 in g_object_get () #11 0x011610c0 in settings_update_resolution () #12 0x011618d4 in gtk_settings_get_for_screen () #13 0x01172250 in gtk_style_init () #14 0x0076e960 in g_type_create_instance () #15 0x0074bf24 in g_object_constructor () #16 0x0074c7a8 in g_object_newv () #17 0x0074d7e8 in g_object_new_valist () #18 0x0074dc88 in g_object_new () #19 0x0122bfac in gtk_widget_get_default_style () #20 0x0122c088 in gtk_widget_init () #21 0x0076ebf8 in g_type_create_instance () #22 0x0074bf24 in g_object_constructor () #23 0x0074c7a8 in g_object_newv () #24 0x0074d7e8 in g_object_new_valist () #25 0x0074dc88 in g_object_new () #26 0x01239cbc in gtk_window_new () #27 0x00006bc0 in NewWindow () at gmain.c:566 #28 0x00006f68 in PrepareWindow () at gmain.c:714 #29 0x0000317c in ShowImage () at pho.c:56 #30 0x000035d4 in NextImage () at pho.c:137 #31 0x000075b0 in main (argc=1, argv=0xbffff7dc) at gmain.c:912 (gdb)

I suspect something in the new xrender Portfile pulling in xorg-libX11 in Tiger/Panther might be causing a problem. If any further info can be of help, please let me know. It also looks like this is a Tiger/Panther specific issue..?

[blb@…]

It could be related to 1.7 always setting MACOSX_DEPLOYMENT_TARGET whereas 1.6 didn't. However, since 1.7 is officially released is this ticket still needed?

[ryandesign (Ryan Carsten Schmidt)]

If this is still an issue with MacPorts 1.7.0, please re-open this ticket.

[(none)]

Milestone Port Bugs deleted