[issue11207] Pythong seg fault with PIL/numpy

2012-07-02 Thread Brett Cannon
Changes by Brett Cannon : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue11207] Pythong seg fault with PIL/numpy

2011-02-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: Judging from the traceback, you should probably report that issue to numpy instead. -- nosy: +pitrou resolution: -> invalid status: open -> pending ___ Python tracker __

[issue11207] Pythong seg fault with PIL/numpy

2011-02-13 Thread David Knapp
David Knapp added the comment: Sorry I'm not all that experienced with gdb. Let me know if there's more to get. (gdb) bt #0 _unaligned_strided_byte_copy (dst=0xcb9623 "\366\377\177", outstrides=1, src= 0x73503da5 , instrides=4969607, N=1, elsize=) at /usr/include/bits/string3

[issue11207] Pythong seg fault with PIL/numpy

2011-02-13 Thread Brett Cannon
Brett Cannon added the comment: Can you give a longer backtrace? Since that failure is happening in a system library we need to know where the segfault first occurs in either PIL, numpy, or CPython. And have you tried this in Python 2.7? -- nosy: +brett.cannon status: open -> pending

[issue11207] Pythong seg fault with PIL/numpy

2011-02-13 Thread David Knapp
New submission from David Knapp : Python had a seg fault with the following simple code. >>> import PIL.Image as Img >>> import numpy as np >>> i = Img.open('/home/falmarri/Dropbox/obey.jpg') >>> n = np.array(bytearray(i.tostring()),dtype=np.uint16) zsh: segmentation fault python Running it un