GNOME Bugzilla – Bug 633257
meld @1.3.1 / @1.4.0 gives a Segmentation Fault
Last modified: 2010-10-30 22:53:22 UTC
Created attachment 173313 [details] crash report from the apple "Report an error" dialog When compiling meld from a clean slate is gives me a Segmentation Fault when running it. I started by following these instructions: http://trac.macports.org/wiki/Migration (Since I recently upgraded to a newer MacBook Pro and now run 64bit OS X 10.6.4 from a previous generation MacBook Pro with OS X 10.5.8 ) I installed meld using macports using the following command: sudo port install meld After fixing a build failure in db46 by following the instructions here: https://trac.macports.org/ticket/26939 (upgrading the Java for Mac OS X 10.6 Update 3 Developer Package), the meld install itself went fine. running the application on the command line like so: $ meld dir1 dir2 Gave me the following output: ========== (process:59542): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Xlib: extension "RANDR" missing on display ":0.0". Segmentation fault sinner:Sites michael$ meld oxodev2 prod_data (process:59655): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale. Xlib: extension "RANDR" missing on display ":0.0". Segmentation fault ========== The page here: http://guide.macports.org/#project.tickets suggests to report the error upstream if the compile and install goes successfully, so I'm doing that here. Attached is the output in the "Report an error dialog" that OS X throws up. I have also tried to upgrade to the 1.4.0 version as described here: http://trac.macports.org/ticket/26808 (by patching the Portfile and running "sudo port upgrade meld") but that resulted in the same error when running the program. I CC'ed the macports maintainer as well, but apparently that doesn't work here.
Did Meld previously work for you under macports? Do any other Gtk+ applications work? I suspect that this isn't a bug with Meld but rather with the environment. If it was a Meld problem, you'd be more likely to see a python traceback instead of getting a segfault. That said, we might be doing something that breaks gtk under X11 on OS X. For what it's worth, I can run Meld under 'native' gtk on OS X (i.e., not using X11).
Hi, Thanks for looking into this. Meld worked previously on my other MacBookPro (not 64 bit). I also recently installed wireshark, which is gtk as well, and that app works. What can I do to debug this further? How do I test meld under native gtk on OS X ?
I've now tested this under macports, and the crash is caused by certain accesses to gobject properties. Specifically, it seems that a crash can be triggered by accessing any gobject property via the x.props.{propertyname} mechanism. For example, you can cause a crash with: >>> import gtk >>> a = gtk.Window() >>> a.show() >>> a.props.title="Foo" >>> print a.props.title The fourth line executes fine; the fifth line crashes. Anyway, the upshot of all of this is that this isn't a bug in Meld. This would appear to be a problem specific to the macports distribution of pygobject. I'd suggest that you file a bug upstream with this additional information. As for running Meld under native gtk, it's not easy. There are instructions on building gtk for OS X at http://gtk-osx.sourceforge.net/ though it's not necessarily straightforward. Once you have a working pygtk built under that framework, running Meld in the jhbuild shell should work fine. Thanks for the bug report.