[issue25336] Segmentation fault on Mavericks consistent crashing of software: Please HELP!!!!!

[CM]

CM added the comment:

I understood what Ned meant, and I did seek advice from the third party 
software creator, it was the first thing I did because like you stated I 
thought it was an issue with the third party software and not python. Coming to 
this bug website was my last resort but I can see that it doesn't make sense

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25336] Segmentation fault on Mavericks consistent crashing of software: Please HELP!!!!!

[R. David Murray]

R. David Murray added the comment:

I think Ned meant "it is *not* likely to be in the python interpreter or 
standard library", and that you should seek help from the third party people 
trying to track down the problem.  *If* it turns out to be python or the 
stdlib, which means you've managed to find a reproducer that does *not* involve 
the third party packages, *then* come back and reopen the issue.

Like Ned said, good luck, but we really can't provide you any more help here 
until the third party packages are eliminated from the equation.

--
nosy: +r.david.murray
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue25336] Segmentation fault on Mavericks consistent crashing of software: Please HELP!!!!!

[CM]

CM added the comment:

Hi Thanks for your response.
So as you have correctly surmised I am using a software package call oof. I ran 
the package using gdb and this is the output that I got. I'm having the same 
issue on i.e. Segmentation fault on three machines, one is a Linux 
Centos/Redhat server (Python 2.7.8), and two macs (python 2.7.10). The gdb 
output below is from the Centos Server machine. 

Again not sure if it helps but I'm only posting all the information I have 
since it wouldn't be entirely easy for me to provide a test case without you 
actually having the software package installed. Thanks in advance. 


---

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffd54c0700 (LWP 22786)]
PyObject_Malloc (nbytes=32) at Objects/obmalloc.c:813
813 Objects/obmalloc.c: No such file or directory.
in Objects/obmalloc.c
Missing separate debuginfos, use: debuginfo-install expat-2.0.1-11.el6_2.x86_64 
fontconfig-2.8.0-3.el6.x86_64 freetype-2.3.11-14.el6_3.1.x86_64 
glibc-2.12-1.149.el6_6.5.x86_64 keyutils-libs-1.4-4.el6.x86_64 
krb5-libs-1.10.3-10.el6_4.6.x86_64 libICE-1.0.6-1.el6.x86_64 
libSM-1.2.1-2.el6.x86_64 libX11-1.6.0-2.2.el6.x86_64 libXau-1.0.6-4.el6.x86_64 
libXcursor-1.1.13-6.20130524git8f677eaea.el6.x86_64 
libXdamage-1.1.3-4.el6.x86_64 libXext-1.3.1-2.el6.x86_64 
libXfixes-5.0-3.el6.x86_64 libXrender-0.9.7-2.el6.x86_64 
libXt-1.1.4-6.1.el6.x86_64 libart_lgpl-2.3.20-5.1.el6.x86_64 
libcom_err-1.41.12-18.el6.x86_64 libgcc-4.4.7-4.el6.x86_64 
libgfortran-4.4.7-4.el6.x86_64 libgnomecanvas-2.26.0-4.el6.x86_64 
libgomp-4.4.7-4.el6.x86_64 libjpeg-turbo-1.2.1-3.el6_5.x86_64 
libpng-1.2.49-1.el6_2.x86_64 libselinux-2.0.94-5.3.el6_4.1.x86_64 
libstdc++-4.4.7-4.el6.x86_64 libtiff-3.9.4-10.el6_5.x86_64 
libuuid-2.17.2-12.14.el6.x86_64 libxcb-1.8.1-1.el6.x86_64 
openssl-1.0.1e-16.el6_5.15.x86_64 zlib-1.2.3-29.el6.x8
 6_64
(gdb) where
#0  PyObject_Malloc (nbytes=32) at Objects/obmalloc.c:813
#1  0x77a90c3d in _PyObject_New (tp=0x77dc3840) at 
Objects/object.c:244
#2  0x77b2cb2d in newlockobject (self=) at 
./Modules/threadmodule.c:164
#3  thread_PyThread_allocate_lock (self=) at 
./Modules/threadmodule.c:746
#4  0x77af3741 in call_function (f=, 
throwflag=) at Python/ceval.c:4017
#5  PyEval_EvalFrameEx (f=, throwflag=) at Python/ceval.c:2679
#6  0x77af54ae in PyEval_EvalCodeEx (co=0x7fffef74bbb0, globals=, locals=, 
args=, argcount=2, kws=0x7fffa40040c8, kwcount=0, 
defs=0x7fffef771068, defcount=1, closure=0x0)
at Python/ceval.c:3265
#7  0x77af365a in fast_function (f=, 
throwflag=) at Python/ceval.c:4129
#8  call_function (f=, throwflag=) at 
Python/ceval.c:4054
#9  PyEval_EvalFrameEx (f=, throwflag=) at Python/ceval.c:2679
#10 0x77af54ae in PyEval_EvalCodeEx (co=0x7fffef75b6b0, globals=, locals=, 
args=, argcount=1, kws=0x7fff5d3de7d8, kwcount=0, 
defs=0x7fffeecdf068, defcount=1, closure=0x0)
at Python/ceval.c:3265
#11 0x77af365a in fast_function (f=, 
throwflag=) at Python/ceval.c:4129
#12 call_function (f=, throwflag=) at 
Python/ceval.c:4054
#13 PyEval_EvalFrameEx (f=, throwflag=) at Python/ceval.c:2679
#14 0x77af54ae in PyEval_EvalCodeEx (co=0x7fffe6669c30, globals=, locals=, 
args=, argcount=3, kws=0x7fff5d3e1bb0, kwcount=0, 
defs=0x7fffe6661fe0, defcount=2, closure=0x0)
at Python/ceval.c:3265
#15 0x77af365a in fast_function (f=, 
throwflag=) at Python/ceval.c:4129
#16 call_function (f=, throwflag=) at 
Python/ceval.c:4054
#17 PyEval_EvalFrameEx (f=, throwflag=) at Python/ceval.c:2679
#18 0x77af54ae in PyEval_EvalCodeEx (co=0x77e2ad30, globals=, locals=, 
args=, argcount=2, kws=0x77f97068, kwcount=0, 
defs=0x0, defcount=0, closure=0x0)
at Python/ceval.c:3265
#19 0x77a73778 in function_call (func=0x7fffeece2938, 
arg=0x7fff563836c8, kw=0x7fff5642b4b0)
at Objects/funcobject.c:526
#20 0x77a441a3 in PyObject_Call (func=0x7fffeece2938, arg=, kw=)
at Objects/abstract.c:2529
#21 0x77af214a in ext_do_call (f=, 
throwflag=) at Python/ceval.c:4346
#22 PyEval_EvalFrameEx (f=, throwflag=) at Python/ceval.c:2718
#23 0x77af54ae in PyEval_EvalCodeEx (co=0x77e342b0, globals=, locals=, 
args=, argcount=2, kws=0x77f97068, kwcount=0, 
defs=0x0, defcount=0, closure=0x0)
at Python/ceval.c:3265
#24 0x77a73778 in function_call (func=0x7fffeece2cf8, 
arg=0x7fff563cf638, kw=0x7fff5642b398)
at Objects/funcobject.c:526
#25 0x77a441a3 in PyObject_Call (func=0x7fffeece2cf8, arg=, kw=)
at Objects/abstract.c:2529
#26 0x77af214a in ext_do_call (f=, 
throwflag=) at Python/ceval.c:4346
#27 PyEval_EvalFrameEx (f=, throwflag=) at Python/ceval.c:2718
---Type  to continue, or q  to quit---

--
status: closed -> open

___
Python tracker 

___
__

[issue25336] Segmentation fault on Mavericks consistent crashing of software: Please HELP!!!!!

[CM]

New submission from CM:

Process: Python [556]
Path:
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Identifier:  Python
Version: 2.7.10 (2.7.10)
Code Type:   X86-64 (Native)
Parent Process:  bash [510]
Responsible: X11.bin [452]
User ID: 502

Date/Time:   2015-10-07 17:01:32.979 -0700
OS Version:  Mac OS X 10.9.5 (13F1096)
Report Version:  11
Anonymous UUID:  34110EFA-E539-3790-15F7-F5AE427C092E

Sleep/Wake UUID: 1444CE38-3698-4FDA-95B9-196B28CB372E

Crashed Thread:  2

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x

VM Regions Near 0:
--> 
__TEXT 00010802b000-00010802d000 [8K] r-x/rwx 
SM=COW  
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib  0x7fff8d24f716 __psynch_cvwait + 10
1   libsystem_pthread.dylib 0x7fff9185dc3b _pthread_cond_wait + 
727
2   org.python.python   0x000108118f51 
PyThread_acquire_lock + 145
3   org.python.python   0x0001080dc74e PyEval_RestoreThread 
+ 62
4   org.python.python   0x000108104f6d PyGILState_Ensure + 
93
5   _gtk.so 0x000108ec4b36 
pygtk_main_watch_check + 50
6   libglib-2.0.0.dylib 0x000108c9efc0 g_main_context_check 
+ 362
7   libglib-2.0.0.dylib 0x000108c9f4ba 
g_main_context_iterate + 388
8   libglib-2.0.0.dylib 0x000108c9f714 g_main_loop_run + 195
9   libgtk-x11-2.0.0.dylib  0x00010918b5db gtk_main + 180
10  _gtk.so 0x000108e7d0ec _wrap_gtk_main + 241
11  org.python.python   0x0001080e1003 PyEval_EvalFrameEx + 
15539
12  org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
13  org.python.python   0x0001080e4c89 fast_function + 297
14  org.python.python   0x0001080e04f5 PyEval_EvalFrameEx + 
12709
15  org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
16  org.python.python   0x0001080e4c89 fast_function + 297
17  org.python.python   0x0001080e04f5 PyEval_EvalFrameEx + 
12709
18  org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
19  org.python.python   0x0001080e4c89 fast_function + 297
20  org.python.python   0x0001080e04f5 PyEval_EvalFrameEx + 
12709
21  org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
22  org.python.python   0x0001080dca16 PyEval_EvalCode + 54
23  org.python.python   0x000108106774 PyRun_FileExFlags + 
164
24  org.python.python   0x0001081062f1 
PyRun_SimpleFileExFlags + 769
25  org.python.python   0x00010811c05e Py_Main + 3070
26  libdyld.dylib   0x7fff8f24c5fd start + 1

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib  0x7fff8d250662 kevent64 + 10
1   libdispatch.dylib   0x7fff90e99421 _dispatch_mgr_invoke 
+ 239
2   libdispatch.dylib   0x7fff90e99136 _dispatch_mgr_thread 
+ 52

Thread 2 Crashed:
0   org.python.python   0x0001080853af PyObject_Malloc + 79
1   org.python.python   0x00010808 _PyObject_New + 18
2   org.python.python   0x00010811e082 
thread_PyThread_allocate_lock + 18
3   org.python.python   0x0001080e1003 PyEval_EvalFrameEx + 
15539
4   org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
5   org.python.python   0x0001080e4c89 fast_function + 297
6   org.python.python   0x0001080e04f5 PyEval_EvalFrameEx + 
12709
7   org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
8   org.python.python   0x0001080e4c89 fast_function + 297
9   org.python.python   0x0001080e04f5 PyEval_EvalFrameEx + 
12709
10  org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
11  org.python.python   0x0001080e4c89 fast_function + 297
12  org.python.python   0x0001080e04f5 PyEval_EvalFrameEx + 
12709
13  org.python.python   0x0001080dd0dd PyEval_EvalCodeEx + 
1725
14  org.python.python   0x000108068b4c function_call + 364
15  org.python.python   0x000108042fa3 PyObject_Call + 99
16  org.python.python   0x0001080e081d PyEval_EvalFrameEx + 
13517
17  org.python.python   0x0001080dd

[issue25336] Segmentation fault on Mavericks consistent crashing of software: Please HELP!!!!!

[Ned Deily]

Ned Deily added the comment:

Without more information or a reproducible test case, it is very difficult to 
say what's going on.  But, from some of the file paths in the crash report, I'm 
guessing you are using a third-party package called OOF2 with a 
MacPorts-installed Python 2.7 and oof2 seems to have some extensions modules 
calling external libraries, like liboof2common.dylib.  There's very little to 
go on but it seems very unlikely that the crash is being caused by a bug in the 
Python interpreter or the Python standard library.  It might be due to 
something your program is doing or it might be some problem with the apparently 
complex mix of third-party libraries and Python.  You *might* have more success 
asking on an OOF mailing list or a MacPorts list but even so I would guess 
that, without a simple reproducible test case that you can share, it may be 
tough to get help.  You also might try running under a debugger like lldb.  
Please re-open this issue if you are able to isolate the problem to the Python 
inte
 rpreter or Python standard library.  Good luck!

--
resolution:  -> third party
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com