Re: [Pyobjc-dev] Snapshots

[Bill B. <bb...@co...>]

I'm able to cause a bus error from just the objc module.  However, the 
actual ObjC interface side of things seems to work fine -- it seems to 
be some kind of a pure Python related problem....

I.e. this works:

 >>> a = objc.runtime.NSMutableArray.array()
 >>> a.addObject_("foo")
 >>> a.addObject_(1)
 >>> a
<NSCFArray objective-c instance 0x70fe70>
 >>> a.description()
'(foo, 1)'

But a basic help(objc) fails mightily (but works on the fink build 
version of pyobjc):

[bumbox:~/bbum-developer/sourceforge/pyobjc] bbum% gdb /usr/bin/python
GNU gdb 5.1-20020408 (Apple version gdb-231) (Tue Aug 13 21:37:39 GMT 
2002)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and 
you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for 
details.
This GDB was configured as "powerpc-apple-macos10".
Reading symbols for shared libraries .... done
(gdb) r
Starting program: /usr/bin/python
[Switching to process 11215 thread 0xb03]
Reading symbols for shared libraries ............. done
Python 2.2 (#1, 07/14/02, 23:25:09)
[GCC Apple cpp-precomp 6.14] on darwin
Type "help", "copyright", "credits" or "license" for more information.
Reading symbols for shared libraries ...... done
 >>> import objc
Reading symbols for shared libraries .......................... done
Reading symbols for shared libraries . done
 >>> help(objc)

Program received signal EXC_BAD_ACCESS, Could not access memory.
0x000707e4 in PyCallIter_New ()
(gdb) bt
#0  0x000707e4 in PyCallIter_New ()
#1  0x000472f4 in PyTuple_GetSlice ()
#2  0x00070af4 in PyCallIter_New ()
#3  0x00070fd0 in PyCallIter_New ()
#4  0x0007128c in PyCallIter_New ()
#5  0x00071c18 in _PyObject_GC_Malloc ()
#6  0x00071c8c in _PyObject_GC_NewVar ()
....

b.bum

On Wednesday, October 9, 2002, at 04:10 PM, Ronald Oussoren wrote:

>
> I've also added a workaround to setup.py that allows you to build 
> pyobjc using Apple's python in Jaguar. However, this doesn't result in 
> a fully workable module: the addressbook.py example causes a coredump 
> :-(, but some of the other examples do work correctly.