Re: [Discuss-gnuradio] GRC on OSX?

[Eric Blossom]

On Wed, Oct 03, 2007 at 03:34:58PM -0400, Michael Dickens wrote:
> Maybe it's the use of python 2.5?
> 
> Has anyone (on this list, or if you know someone) ever used GRC on  
> OSX?  As I said, I've never tried to until this morning.
> 
> >1) I suppose numbersink2 is not in your particular gnuradio build.
> >Checkout the trunk again.
> 
> Done.  Nothing changed.
> 
> >2) There is no config file when you first load GRC. When you close
> >GRC, it will create the config file, and the error will be gone
> >thereafter.
> 
> OK.  I went ahead and did "touch ~/.grc.xml", which makes that  
> message go away.  No change in execution.
> 
> >3) Bus Error? I have no idea... There are no "un-intialized"
> >variables. And the code that loads the preferences isnt printing this.
> >It might be a weird GTK+OSX thing. Does GRC function otherwise?
> 
> Running gdb comes back with:
> 
> (gdb) run Editor.py
> [snip]
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
> 0x0024ed8b in PyString_FromString (str=0x0) at Objects/stringobject.c: 
> 108
> 108     Objects/stringobject.c: No such file or directory.
>         in Objects/stringobject.c
> (gdb) bt
> #0  0x0024ed8b in PyString_FromString (str=0x0) at Objects/ 
> stringobject.c:108
> #1  0x002b8f84 in PyModule_AddStringConstant (m=0x9030490,  
> name=0x909a8d0 "XML_ERROR_UNBOUND_PREFIX", value=0x0) at Python/ 
> modsupport.c:630
> #2  0x09092ea3 in initpyexpat () at extensions/pyexpat.c:1977
> #3  0x002b40bb in _PyImport_LoadDynamicModule (name=0xbfffaddb  
> "xml.parsers.pyexpat", pathname=0xbfffa927 "/opt/local/lib/python2.5/ 
> site-packages/_xmlplus/parsers/pyexpat.so", fp=0xa000bea8) at ./ 
> Python/importdl.c:53
> #4  0x002b1d9d in load_module (name=0xbfffaddb "xml.parsers.pyexpat",  
> fp=0x1b, buf=0xbfffa927 "/opt/local/lib/python2.5/site-packages/ 
> _xmlplus/parsers/pyexpat.so", type=3, loader=0x0) at Python/import.c: 
> 1752

In the random stab in the dark department: I wonder if the problem is
in pyexpat.c, and whether it was compiled with -O1 optimization on the
PPC.  (Somebody really ought to create a small test case for the gcc
guys and log a bug.)

Is there QA code for pyexpat and does it pass (make check?)

Eric