[PEAK] Problem running pyprotocols on OS X Leopard 10.5.2

[Akira Kitada]

Reinstalling Python2.4 fixed this problem...
Maybe MacPorts's problem?

Sorry and thanks for your help.

On Sat, Mar 29, 2008 at 12:14 PM, Phillip J. Eby <pje at telecommunity.com> wrote:
>
> At 10:18 AM 3/29/2008 +0900, Akira Kitada wrote:
>  >Hi,
>  >
>  >I'm trying to porting PyProtocols 1.0a0dev-r2302 for MacPorts, Port
>  >collections of Mac OS X.
>  >it works with Python2.5 but it doesn't with Python2.4
>  >
>  >$ /opt/local/bin/python2.4
>  >Python 2.4.5 (#1, Mar 23 2008, 02:29:58)
>  >[GCC 4.0.1 (Apple Inc. build 5465)] on darwin
>  >Type "help", "copyright", "credits" or "license" for more information.
>  > >>> import protocols
>  > >>> help(protocols)
>  >Bus error
>  >
>  >Here's the trace
>  >
>  >Thread 0 Crashed:
>  >0   readline.so                         0x000a7aa3 call_readline + 691
>  >1   org.python.python                   0x0016b7ae PyOS_Readline + 254
>  >2   org.python.python                   0x0016cd70 tok_nextc + 64
>  >3   org.python.python                   0x0016d5a5 PyTokenizer_Get + 101
>  >4   org.python.python                   0x00168312 parsetok + 210
>  >5   org.python.python                   0x00212942
>  >PyRun_InteractiveOneFlags + 290
>  >6   org.python.python                   0x00212b63
>  >PyRun_InteractiveLoopFlags + 99
>  >7   org.python.python                   0x00213a19 PyRun_AnyFileExFlags + 185
>  >8   org.python.python                   0x0021da8a Py_Main + 3130
>  >9   org.python.python                   0x000018dc 0x1000 + 2268
>  >10  org.python.python                   0x00001809 0x1000 + 2057
>  >
>  >
>  >Do you have any related report on this?
>
>  No, sorry.  What about the test suite?  Does it do the same thing?  I
>  do not have this problem with Python 2.4 on Windows, haven't tried
>  any other platforms and don't have a Mac in any case.  Are you
>  building PyProtocols with or without the "speedups" enabled?  (e.g.
>  setup.py --with-speedups install vs. setup.py --without-speedups
>  install).   You might see if that makes a difference, but be sure to
>  completely clean your build tree (i.e. rm -rf build) in between the
>  two installs.
>
>