Mabot causing seg fault on Mac OS X

[GoogleCodeExporter]

Mabot causing seg fault on Mac OS X

[GoogleCodeExporter]

Based on the segfault information the problem seems to be related to the Tkinter
toolkit used by Mabot. A quick Google search with terms "tkinter osx segfault"
returns several results indicating there are some problem with it on Snow 
Leopard.
Could you jerry57 try searching for more information and see can you find a 
solution?

Original comment by pekka.klarck on 19 Mar 2010 at 8:58

[GoogleCodeExporter]

I have tried looking around to find a solution to the segfault, but no luck 
yet.  If
anyone else spots something they think might work, please let me know and I 
will give
it a try.  Unfortunately I am not a programmer but am willing to try whatever I 
can.

Original comment by [email protected] on 23 Mar 2010 at 1:08

[GoogleCodeExporter]

I tried this from my Leopard (10.5.8) desktop and MaBot runs without error.  
Here are
the versions I have installed there.
python --version
Python 2.5.1
pybot --version
Robot Framework 2.1.3 (Python 2.5.1 on darwin)
jython --version
Jython 2.5.1
mabot.py --version
Mabot 0.6.1

I only briefly used it to open one of my existing test suites and click through 
it. 
Will try and do further testing as time permits, but would really love to 
resolve
this issue for Snow Leopard (10.6.2).

Original comment by [email protected] on 23 Mar 2010 at 2:30

[GoogleCodeExporter]

It might be that the problem is in disabling Text object. See 
http://stackoverflow.com/questions/2914603/why-do-i-get-a-segmentation-fault-whi
le-redirecting-sys-stdout-to-tkinter-text-wi for more details. We check is this 
the case and if it is easy to fix, we will do it for 0.7 release.

Original comment by [email protected] on 28 Jun 2010 at 7:10

• Changed state: Accepted
• Added labels: Target-0.7

[GoogleCodeExporter]

Seems that this is not the case in here. We were able to reproduce the problem. 
We will investigate what is causing the problem before releasing Mabot 0.7. 

Original comment by [email protected] on 28 Jun 2010 at 7:49

[GoogleCodeExporter]

The segmentation fault first rises when calling idlelib's 
TreeWidget.TreeNode.update(), which internally uses Tcl/Tk. If I comment this 
call out, I get the segmentation fault again from a different part of the gui, 
but finally it always ends up coming from Tcl/Tk.

If I try run the code through a debugger I dont get the segmentation fault 
anymore. This seems to suggest that the problem is related to threads and 
concurrency problems in Tcl/Tk with Snow Leopard.

Unfortunately I can't now use more time trying to figure this out. For the time 
being we at the core team have to leave this problem open and unsolved. It 
would be great if anyone with a Mac can lend a hand and investigate this 
further.

Original comment by [email protected] on 2 Jul 2010 at 12:49

• Removed labels: Target-0.7

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

What are the chances of converting MaBot to use wx rather than tk?  wx (which 
RIDE uses) does not seem to have the problems that tk is suffering on Mac OS X 
10.6.

Original comment by [email protected] on 28 Sep 2010 at 5:26

[GoogleCodeExporter]

I personally don't know what is involved to do this switch, but I have asked 
one of our python devs here to take a look at this.  I will post whatever he 
reports back.

Original comment by [email protected] on 28 Sep 2010 at 5:54

[GoogleCodeExporter]

attached more info


Process:         Python [2514]
Path:            
/System/Library/Frameworks/Python.framework/Versions/2.6/Resources/Python.app/Co
ntents/MacOS/Python
Identifier:      org.python.python.app
Version:         2.6 (2.6)
Build Info:      python-440100~2
Code Type:       X86 (Native)
Parent Process:  bash [1572]

Date/Time:       2010-10-25 14:19:46.889 +0800
OS Version:      Mac OS X 10.6.4 (10F569)
Report Version:  6

Interval Since Last Report:          291098 sec
Crashes Since Last Report:           13
Per-App Interval Since Last Report:  7045 sec
Per-App Crashes Since Last Report:   2
Anonymous UUID:                      6F7F4C56-443C-4063-8D8A-40F0CBBA12EA

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000065726f46
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   ???                             0x65726f46 0 + 1701998406
1   Tcl                             0x010794e4 Tcl_FindCommand + 840
2   Tcl                             0x010100df Tcl_GetCommandInfo + 51
3   Tk                              0x011ae475 TkpGetSubFonts + 5008
4   com.apple.AE                    0x9764ff58 aeDispatchAppleEvent(AEDesc 
const*, AEDesc*, unsigned long, unsigned char*) + 166
5   com.apple.AE                    0x9764fe57 dispatchEventAndSendReply(AEDesc 
const*, AEDesc*) + 43
6   com.apple.AE                    0x9764fd61 aeProcessAppleEvent + 197
7   com.apple.HIToolbox             0x989d1323 AEProcessAppleEvent + 50
8   com.apple.AppKit                0x9090ccc6 _DPSNextEvent + 1420
9   com.apple.AppKit                0x9090c2ca -[NSApplication 
nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
10  Tk                              0x011b6e94 XQueryPointer + 2261
11  Tk                              0x011b73d6 Tk_MacOSXSetupTkNotifier + 1079
12  Tcl                             0x0107ea57 Tcl_DoOneEvent + 229
13  Tk                              0x010f834e TkGetDisplayOf + 424
14  Tcl                             0x0101196b Tcl_CreateInterp + 4919
15  Tcl                             0x01012960 Tcl_EvalObjv + 72
16  _tkinter.so                     0x007cd49d Tkapp_CallDeallocArgs + 11750
17  org.python.python               0x0008b382 PyEval_EvalFrameEx + 16375
18  org.python.python               0x0008b4e5 PyEval_EvalFrameEx + 16730
19  org.python.python               0x0008b4e5 PyEval_EvalFrameEx + 16730
20  org.python.python               0x0008b4e5 PyEval_EvalFrameEx + 16730
21  org.python.python               0x0008b4e5 PyEval_EvalFrameEx + 16730
22  org.python.python               0x0008b4e5 PyEval_EvalFrameEx + 16730
23  org.python.python               0x0008cf74 PyEval_EvalCodeEx + 1720
24  org.python.python               0x0002ee0c PyClassMethod_New + 1823
25  org.python.python               0x0000c6e0 PyObject_Call + 101
26  org.python.python               0x0001c10d PyClass_New + 1603
27  org.python.python               0x0000c6e0 PyObject_Call + 101
28  org.python.python               0x0008678a PyEval_CallObjectWithKeywords + 
171
29  org.python.python               0x0001ba37 PyInstance_New + 290
30  org.python.python               0x0000c6e0 PyObject_Call + 101
31  org.python.python               0x0008c812 PyEval_EvalFrameEx + 21639
32  org.python.python               0x0008b4e5 PyEval_EvalFrameEx + 16730
33  org.python.python               0x0008cf74 PyEval_EvalCodeEx + 1720
34  org.python.python               0x0008d019 PyEval_EvalCode + 87
35  org.python.python               0x000a40af Py_CompileString + 111
36  org.python.python               0x000a415b PyRun_FileExFlags + 139
37  org.python.python               0x000a5e7e PyRun_SimpleFileExFlags + 814
38  org.python.python               0x000b315c Py_Main + 3074
39  org.python.python.app           0x00001eb5 start + 53

Thread 1:  Dispatch queue: com.apple.libdispatch-manager
0   libSystem.B.dylib               0x94791942 kevent + 10
1   libSystem.B.dylib               0x9479205c _dispatch_mgr_invoke + 215
2   libSystem.B.dylib               0x94791519 _dispatch_queue_invoke + 163
3   libSystem.B.dylib               0x947912be _dispatch_worker_thread2 + 240
4   libSystem.B.dylib               0x94790d41 _pthread_wqthread + 390
5   libSystem.B.dylib               0x94790b86 start_wqthread + 30

Thread 2:
0   libSystem.B.dylib               0x947909d2 __workq_kernreturn + 10
1   libSystem.B.dylib               0x94790f68 _pthread_wqthread + 941
2   libSystem.B.dylib               0x94790b86 start_wqthread + 30

Thread 3:
0   libSystem.B.dylib               0x9478a086 select$DARWIN_EXTSN + 10
1   Tcl                             0x010b472b Tcl_InitNotifier + 1643
2   libSystem.B.dylib               0x9479881d _pthread_start + 345
3   libSystem.B.dylib               0x947986a2 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x0181fab4  ebx: 0x01078aea  ecx: 0x0181faa0  edx: 0xbfffcc26
  edi: 0xbfffcc24  esi: 0x011dd172  ebp: 0xbfffcd08  esp: 0xbfffcbbc
   ss: 0x0000001f  efl: 0x00010206  eip: 0x65726f46   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x65726f46

Original comment by [email protected] on 25 Oct 2010 at 6:23

[GoogleCodeExporter]

I'm running into this issue as well. Would love a fix.

Original comment by [email protected] on 12 Jun 2012 at 10:26

[GoogleCodeExporter]

Currently OSX support is not in the scope of core teams tasks.

Patches are welcome!

Original comment by [email protected] on 11 Oct 2012 at 1:07