ODI fails when running MAXL scripts

HI,
We have a problem with ODI where when a scenario has a maxl script as a step the scenario fails.
This is not a problem in our production environment but it is present in our DEV and TEST environments. We believe it may be a problem with the cloning process from PROD.
Has anyone had this issue previously or can provide some helpful direction.
Regards
Luke
ODI 10.1.3.5

What is the error you are getting at the failure point?

Similar Messages

  • Deployment failing when running .bat script or command line file package

    HI Guys,
    I am trying to run a .bat file on a client using a program. My data source point to the script's folder.
    I keeps failing with error 1. 
    I have trying making run in 64-bit using this without luck: http://madluka.wordpress.com/2012/09/24/configmgr-2012-64bit-file-system-redirection-bites-again/
    Here is the content of my .bat file:
    @ECHO OFF
    IF NOT "%PROCESSOR_ARCHITEW6432%"=="AMD64" GOTO native
      ECHO "Re-launching Script in Native Command Processor..."
      %SystemRoot%\Sysnative\cmd.exe /c %0 %*
      EXIT
    :native
    ECHO "Running Script in Native Command Processor..."
    c:\
    cd c:\windows\System32
    start cmd.exe /c shutdown -l
    stop
    I will get the same error when running a simply command line as well. Instead of a .bat file.
    any ideas?

    Maybe this will help you:
    http://blog.coretech.dk/kea/configuration-manager-shutdown-utility
    This instead of using "shutdown.exe -l" command. This tool can be used for logoff also. Hope it helps!
    My blogs: Henk's blog and
    Virtuall | Follow Me on:
    Twitter | View My Profile on:
    LinkedIn

  • 11gR2 RAC install fail when running root.sh script on second node

    I get the errors:
    ORA-15018: diskgroup cannot be created
    ORA-15072: command requires at least 2 regular failure groups, discovered only 0
    ORA-15080: synchronous I/O operation to a disk failed
    [main] [ 2012-04-10 16:44:12.564 EDT ] [UsmcaLogger.logException:175] oracle.sysman.assistants.util.sqlEngine.SQLFatalErrorException: ORA-15018: diskgroup cannot be created
    ORA-15072: command requires at least 2 regular failure groups, discovered only 0
    ORA-15080: synchronous I/O operation to a disk failed
    I have tried the fix solutions from metalink note, but did not fix issue
    11GR2 GRID INFRASTRUCTURE INSTALLATION FAILS WHEN RUNNING ROOT.SH ON NODE 2 OF RAC USING ASMLIB [ID 1059847.1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Hi,
    it looks like, that your "shared device" you are using is not really shared.
    The second node does "create an ASM diskgroup" and create OCR and Voting disks. If this indeed would be a shared device, he should have recognized, that your disk is shared.
    So as a result your VMware configuration must be wrong, and the disk you presented as shared disk is not really shared.
    Which VMWare version did you use? It will not work correctly with the workstation or player edition, since shared disks are only really working with the server version.
    If you indeed using the server, could you paste your vm configurations?
    Furthermore I recommend using Virtual Box. There is a nice how-to:
    http://www.oracle-base.com/articles/11g/OracleDB11gR2RACInstallationOnOEL5UsingVirtualBox.php
    Sebastian

  • I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build.  The same call works fine when running on the device

    I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
    I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
    The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
    I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
    I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
    By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
    Anyone have an idea on other things to try to debug/resolve this?
    Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
    Thanks!

    After a week's worth of debugging, I found the issue.
    The Java type returned from the call was defined as ArrayList.  Changing it to List resolved the problem.
    I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid.  And, why it works in Debug mode and not in Release build is even stranger.  Maybe someone can shed some light on the logic here to me.

  • LSMW Fails when run in B/G but works fine in Front end..why?

    Hi All,
    i am trying to run a batch process by LSMW, my files are accurate, no problem with them, everything works fine but it fails when run in BG..works absolutely fine in front end. whats the diff with running in B/G?
    same thing happens when i am trying to execute an RFC thru SAP JCO, it works when debugger is on (i guess switching on debugger is similar to running in B/G) but it doesnt work when debugger is off. but when i execute that RFC directly in se37 from SAP gui it works fine..fails when connected to JCO..
    i am not having this issue with r/3 4.6c or mySAP ECC.6.0  i have this issue only in r/3 4.7.
    has anyone faced the similar situtaion? pls help.
    thanks.
    p.s if this may help. the RFC and LSMW error both are pertaining to change in address of US employees.( infotype 0006)

    Applying  SAP note 928273 Solved this issue.

  • LSMW fails when run in B/G works fine in Frontend..why?

    Hi All,
    i am trying to runa batch process by LSMW, my files are accurate, no problem with them, everything works fine but it fails when run in BG..works absolutely fine in front end. whats the diff with running in B/G?
    same thing happens when i am trying to execute an RFC thru SAP JCO, it works when debugger is on 9i guess switching on debugger is similar to running in B/G) but it doesnt work when debugger is off. but when i execute that RFC directly in se37 from SAP gui it works fine..fails when connected to JCO..
    i am not having this issue with r/3 4.6c or mySAP ECC.6.0  i have this issue only in r/3 4.7.
    has anyone faced the similar situtaion? pls help.
    thanks.
    p.s if this may help. the RFC and LSMW error both are pertaining to change in address of US employees.( infotype 0006)

    for LSMW its the recording of transaction PA40 (employee hire fails when filling  address details) and PA30 (change address) and same is the case with RFC..well its a BAPI_ADDRESSEMPUS_CHANGE. 
    To eloborate more..the error is..Fill in all the mandatory fields.
    which i am very much doing..there are no hidden fields or anything..i have seen the screens etc..I AM filling all mandatory fields. infact i am not leaving anything unfilled., same scrren is going fine when in front end..i am just clicking ok..ok..ok and boom transaction complete..no complaints. but running B/G is killing me.
    i have to run batch for 100,000 employees
    What fails my logic is..its working fine in 4.6c and mySAP ECC.6.0 but not in 4.7
            Hruser
    Message was edited by:
            Hruser

  • LSMW fails when run in B/G but works in Frontend..why?

    Hi All,
    i am trying to runa batch process by LSMW, my files are accurate, no problem with them, everything works fine but it fails when run in BG..works absolutely fine in front end. whats the diff with running in B/G?
    same thing happens when i am trying to execute an RFC thru SAP JCO, it works when debugger is on 9i guess switching on debugger is similar to running in B/G) but it doesnt work when debugger is off. but when i execute that RFC directly in se37 from SAP gui it works fine..fails when connected to JCO..
    i am not having this issue with r/3 4.6c or mySAP ECC.6.0  i have this issue only in r/3 4.7.
    has anyone faced the similar situtaion? pls help.
    thanks.
    p.s if this may help. the RFC and LSMW error both are pertaining to change in address of US employees.( infotype 0006)

    Applying SAP note 928273 Solved this issue.
    thank you.

  • Call failing at Run External Script

     Dear All,
    i installed UCCE with CVP (Ver 10.0.1). 
    Call Flow CME-->VXML GW-->CVP-->ICM. But call is failing at run External script. I am attaching CVP error Log and ICM Script.
    pls suggest.
    1469: 10.35.133.129: Sep 16 2014 11:19:38.981 +0530: %CVP_10_0_IVR-3-CALL_ERROR:  CALLGUID=044224283C9A11E4803A30F70D96B740 DNIS=11111111116 Media Fetch Error for URL=file://../MediaFiles/en-us/app/Welcome.wav (Client: 10.35.133.194) [id:3023] 
    1470: 10.35.133.129: Sep 16 2014 11:19:38.981 +0530: %CVP_10_0_IVR-3-CALL_ERROR:  RunScript Error from 10.35.133.194 [MEDIA_FILE_NOT_FOUND(9)] CALLGUID: 044224283C9A11E4803A30F70D96B740 DNIS=11111111116 {VRUScriptName: 'PM,Welcome,A' ConfigParam: 'Y'} [id:3023] 
    2285: 10.35.133.129: Sep 16 2014 11:19:38.996 +0530: %CVP_10_0_SIP-3-SIP_ERROR_SNMP:  B2BUA is not configured with a route for making calls to [91919191]. Please add this route. [id:5010] 
    1487: 10.35.133.129: Sep 16 2014 11:19:41.087 +0530: %CVP_10_0_IVR-3-CALL_ERROR:  Removing CALLGUID: 044224283C9A11E4803A30F70D96B740 DNIS=1111111111 due to exception in CallNewHandler. (Client: 10.35.133.194) Received ICM DialogFailure response for new call request. DialogFailure StatusCode: 15 HTTP req: { RECOVERY_VXML=flash:recovery.vxml, CALL_DNIS=1111111111, CALL_UUI=, MSG_TYPE=CALL_NEW, ERROR_CODE=NONE(0), CALL_ID=044224283C9A11E4803A30F70D96B740, CLIENT_TYPE=IOS, CALL_ANI=sip:[email protected]:5060 } [id:3023] 
    1496: 10.35.133.129: Sep 16 2014 11:19:42.117 +0530: %CVP_10_0_IVR-3-CALL_ERROR:  Removing CALLGUID: 044224283C9A11E4803A30F70D96B740 DNIS=1111111111 due to exception in CallNewHandler. (Client: 10.35.133.194) Received ICM DialogFailure response for new call request. DialogFailure StatusCode: 15 HTTP req: { RECOVERY_VXML=flash:recovery.vxml, CALL_DNIS=1111111111, CALL_UUI=, MSG_TYPE=CALL_NEW, ERROR_CODE=NONE(0), CALL_ID=044224283C9A11E4803A30F70D96B740, CLIENT_TYPE=IOS, CALL_ANI=sip:[email protected]:5060 } [id:3023] 
    1505: 10.35.133.129: Sep 16 2014 11:19:43.146 +0530: %CVP_10_0_IVR-3-CALL_ERROR:  Removing CALLGUID: 044224283C9A11E4803A30F70D96B740 DNIS=1111111111 due to exception in CallNewHandler. (Client: 10.35.133.194) Received ICM DialogFailure response for new call request. DialogFailure StatusCode: 15 HTTP req: { RECOVERY_VXML=flash:recovery.vxml, CALL_DNIS=1111111111, CALL_UUI=, MSG_TYPE=CALL_NEW,
    Regards,
    Mukesh Singh

    You have media fetch error,the URL being formed is below:
    file://../MediaFiles/en-us/app/Welcome.wav
    should be something like http://x.x.x.x/en-us/app/welcome.wav
    also please share your full CVP logs for the call.
    it is always annoying to see b2b user agent is not configured, so please configure ringtone and error label to sent to proper VXML gateway.
    regards
    Chintan

  • Error when running child script in starter kit

    Hi all,
    When i playback the starter kit hr scripts it is showing the following error...
    Failure when running child script hr_tsk_hr_0001a.
    Can anyone tell why this error is occuring.

    Glad to read you got beyond the initial URL. I can't even get beyond that. Oh well.

  • Scripts that work in VSTS IDE fails when run through MTM.

    Hi, we have created scripts using VSTS Coded UI that work well when triggered from VSTS IDE itself. But when we trigger them through MTM and executed from Agent Machine, it seems that some controls are not being identified properly. This is causing scripts
    to fail intermittently.
    When we re run the script again, it passes. this behaviour is inconsistent.
    Since this issue does not occur in VSTS, it has to be somehow linked to how the scripts work through MTM. any guidance on this will be much appreciated

    Hi Vasanth,
    Thank you for posting in MSND forum.
    >>But when we trigger them through MTM and executed from Agent Machine, it seems that some controls are not being identified properly. This is causing scripts to fail intermittently.
    According to your issue, could you please share me the detailed error message after you run coded UI test some controls failed through MTM?
    In addition, as you said that since this coded UI test script work well by the VSTS IDE, so the issue is not related to the coded UI test project itself.
    Therefore, to check if this issue is related to the lab environment, I suggest you could try to create a simple coded UI test from VSTS IDE and then ensure the simple coded UI test work well from the VSTS IDE.
    Then, you could try to run this simple coded UI test by MTM and then check if you could run the simple coded UI test fine.
    (1) If you still could not run simple coded UI test well, I suggest you could try to restart your test agent machine and then check this issue again.
    (2) If you could run this simple coded UI test, I suggest you could to make Coded UI Tests Wait For Specific Events and then check this issue again.
    https://msdn.microsoft.com/en-us/library/gg131072.aspx?f=255&MSPPError=-2147217396
    In addition, if you are testing the web application for coded UI test, please try to check if the test agent machine's IE browser is same with the local VS machine. Sometime, the different version of IE will impact the coded UI test.
    If you have any update message about your issue, please free fell let to me know.
    Best Regards,
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Deploying the Custom Worklist Application When run ant script Fail

    Hi
    I have tried to deploy worklist application on Oracle SOA Suite to custom it and I have follow the BPEL Process Manager Developer's Guide (10.1.3.1.0) in chapter 16 topic 16.5.1.5. Deploy the Custom Worklist Application but whenI tried to run ant script to deploy custom worklist application, the error has occur "Unexpected element "echo" ". I access to build.xml file to comment element echo out and run ant again but the new error has occured "The <fail> task doesn't support the nested "condition" element." . How should I do for deploy custom application ?
    I use ant -version to check ant version and message has show "Apache Ant version 1.5.2-23 compiled on November 12 2003"
    Please help me!
    Thanks
    Message was edited by:
    user520932

    Hi ,
    I am facing the same issue. Were u able to solve this ?

  • Opening Excel Workbook Fails when run from Scheduled Task on Windows Server 2008 Rw

    Hi,
    I have a little vbs script that instantiates the Excel.Application object and then opens a work book to perform some tasks on it. The script runs fine when run from the command line. When I attempt to run it as a scheduled task (it is supposed to update
    data that is pulled from a SQL Server at regular intervals), it fails with the following error:
    Microsoft Office Excel cannot access the file 'c:\test\SampleWorkbook.xlsm'. There are several possible reasons: .....
    The file does exist. The path reported in the error is correct. The account under which the task is running is the same account I use to run it from the command line. User Account Control is not enabled, and the task is set up to run with highest privileges.
    When I run the same script through the Task Scheduler from a Windows Server 2003 machine, it works without issue.
    I was just wondering if somebody on this forum has run into a similar issue in connection with Windows Server 2008 R2 and figured out what the magic trick is to make it work. I'm sure it is rights related, but I haven't quite figured out what which rights
    are missing.
    Thanks in advance for any advice you may have.

    This is truly killing me ... trying to get it working on Windows Server 2012 without success.
    I desperately need to automate running Excel macros in a "headless" environment, that is non-interactive, non-GUI, etc.
    I can get it to work using Excel.Application COM, either via VBScript or Powershell, successfully on many other Windows systems  in our environment - Windows Server 2008 R2, Windows 7 (32-bit), etc.,  -BUT-
    The two servers we built out for running our automation process are Windows Server 2012 (SE) - and it just refuses to run on the 2012 servers - it gives the messages below from VBScript and PowerShell, respectively- 
    I have tried uninstalling and re-installing several different versions of Microsoft Excel (2007 Standard, 2010 Standard, 2010 Professional Plus, 32-bit vs. 64-bit, etc.), but it makes no difference.
    Would be extremely grateful if any one out there has had any success in running Excel automation on Server 2012 in a non-interactive environment that they could share.
    ( I have tried adding the "%windir%\syswow64\config\systemprofile\desktop"
    folder, which did fix the issue for me when testing on Windows Server 2008 R2, but sadly did not resolve it on Windows Server 2012 )
    [VBScript error msg]
    Z:\TestExcelMacro.vbs(35, 1) Microsoft Office Excel: Microsoft Office Excel cannot
    access the file 'Z:\TestExcelMacro.xlsm'. There are several possible reasons:
    • The file name or path does not exist.
    • The file is being used by another program.
    • The workbook you are trying to save has the same name as a currently open work
    [Powershell error msg]
    Exception calling "Add" with "0" argument(s): "Microsoft Office Excel cannot open or save any more documents because th
    ere is not enough available memory or disk space.
     To make more memory available, close workbooks or programs you no longer need.
     To free disk space, delete files you no longer need from the disk you are saving to."
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : ComMethodTargetInvocation
    You cannot call a method on a null-valued expression.
        + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
        + FullyQualifiedErrorId : InvokeMethodOnNull

  • Error when running a script using upsshell.exe

    I have a simple custom script which is
    Sub Test1()
    Set fso=  CreateObject("Scripting.filesystemobject")
    Set ts = fso.CreateTextFile("D:\DATA\****\Outbox\Templates\Test.txt")
    ts.writeline "hi"
    End sub
    When I am running it manually in workbench, the script runs fine but when I try to run it using upsshell.exe(command provided below)
    D:\Oracle\MIDDLE~1\EPMSYS~1\products\FINANC~2\SHARED~1\upsShell.exe CustomScriptEx=****~admin~****~~****~D:\DATA\test\Outbox\Logs~Test1~1033~0
    i get the following error
      ERROR:
        Code............ 438
        Description..... [Script failure caused error]: Object doesn't support this property or method
        Procedure....... modupsShell.ExecuteCustomScriptEx
        Component....... upsShell
        Version......... 1112
        Process ID...... 292496
        Thread.......... 290292
      IDENTIFICATION:
        User............ admin
        Domain..........
        Computer Name... *******
        App Name........ ****
      PROCEDURE STEPS:
        1-Split Arguments
        2-Create Load balancer=*******
        3-Authenticate
        4-Get Next App Server
        5-Open App Server=*******
        6-Execute the script=Test1
        7-Step was not reached, a previous step failed
    Any ideas on the error?

    Hello Verdulken,
    I have a few additional questions:
    Does your application function correctly when running the LabVIEW operator interface you have created as a VI in the LabVIEW development environment (i.e. does this problem only occur when the LabVIEW operator interface is run as an executable)?
    What is the error that you are receiving?
    Regarding the VI that you open programmatically, do you open it in a visible manner (i.e. use the Show front panel when called option from VI Properties)?If so, do you also close this VI after it finishes (i.e. use the Close if originally closed option from VI Properties)?
    Does the error occur on the step that calls this very same VI again later in the sequence?
    Does your application function correctly if you use the development adapter for all of your calls?
    Thank you in advance for this information,
    Matt G.
    National Instruments
    Applications Engineering

  • Running MaxL scripts

    I was helping a client with automating the running of a MaxL script, using the Windows AT command, and we encountered something odd: a MaxL script that runs fine in EAS does not run correctly when invoked programmatically.This seems to occur when the script involves path references (for error file locations, etc.). Surrounding the path (which had no spaces or "funny" characters) with single quotes works in a script that is to be run from the EAS console.However, when the script is run programmatically (through a batch file, or the AT command), it seems that you have to surround paths with--get this:First: single quotes, to denote the stringSecond: double quotes (outside the single quotes), for a reason a can't quite put into wordsThird: the backslash character used in Windows path references is an escape character in MaxL, so to actually refer to a backslash, you have to use two of them in a row.So, the path used in error writing was originally written in the script like this: 'D:\Errors\DimBuild.err'...and to run programmatically, it had to be:"'D:\\Errors\\DimBuild.err'"...and the problem is, the latter example will NOT run from EAS. Has anyone else encountered this issue?Jared

    I've found that to use a windows path in MAXL, I've found by trial and error that the form that works is'\\\\server05\essbase\buddb\budapp\dataload.txt'Don't know why, but the double backslashes preceding the server need to be escaped, but the subsequent ones don't. I discovered this by trial and error and carefully reading error output.And of course shell statements don't work from EAS.

  • Unexpected error when running Python scripts?

    I always get this crash when I try to run python scripts. Anyone know what is causing this or how to fix it?
    Process:         Python [8022]
    Path:            /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/C ontents/MacOS/Python
    Identifier:      Python
    Version:         2.7.2 (2.7.2)
    Code Type:       X86-64 (Native)
    Parent Process:  ??? [1]
    User ID:         501
    Date/Time:       2012-11-23 05:13:46.990 -0700
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Interval Since Last Report:          62859 sec
    Crashes Since Last Report:           6
    Per-App Crashes Since Last Report:   4
    Anonymous UUID:                      9A83E25A-0D91-6DC9-960B-E7126A515A89
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x00007faa1b19ad5e
    VM Regions Near 0x7faa1b19ad5e:
        MALLOC_TINY            00007faa1b000000-00007faa1b100000 [ 1024K] rw-/rwx SM=COW 
    -->
        MALLOC_SMALL           00007faa1b800000-00007faa1c800000 [ 16.0M] rw-/rwx SM=COW 
    Application Specific Information:
    *** single-threaded process forked ***
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_c.dylib                       0x00007fff87fafde1 tiny_free_list_add_ptr + 112
    1   libsystem_c.dylib                       0x00007fff87fb354e tiny_malloc_from_free_list + 1078
    2   libsystem_c.dylib                       0x00007fff87fb3ad8 szone_malloc_should_clear + 971
    3   libsystem_c.dylib                       0x00007fff87fa6153 malloc_zone_malloc + 71
    4   libsystem_c.dylib                       0x00007fff87fa6c61 realloc + 82
    5   org.python.python                       0x00000001065e6ac9 0x10658b000 + 375497
    6   org.python.python                       0x00000001065e4b23 0x10658b000 + 367395
    7   org.python.python                       0x00000001065e6646 0x10658b000 + 374342
    8   org.python.python                       0x00000001065a4494 PyEval_EvalFrameEx + 8967
    9   org.python.python                       0x00000001065a2147 PyEval_EvalCodeEx + 1934
    10  org.python.python                       0x00000001065dbd7a 0x10658b000 + 331130
    11  org.python.python                       0x000000010659a6c6 PyObject_Call + 97
    12  org.python.python                       0x00000001065b79bf 0x10658b000 + 182719
    13  org.python.python                       0x000000010659a6c6 PyObject_Call + 97
    14  org.python.python                       0x00000001065a8018 PyEval_CallObjectWithKeywords + 177
    15  org.python.python                       0x00000001065ba46e PyCodec_Encode + 78
    16  org.python.python                       0x0000000106633978 PyUnicodeUCS2_AsEncodedString + 141
    17  org.python.python                       0x00000001065c232f 0x10658b000 + 226095
    18  org.python.python                       0x00000001065c0c91 0x10658b000 + 220305
    19  org.python.python                       0x00000001065bfc43 0x10658b000 + 216131
    20  org.python.python                       0x00000001065bff0d PyArg_ParseTuple + 143
    21  _socket.so                              0x0000000106b2c7f3 0x106b28000 + 18419
    22  _socket.so                              0x0000000106b2b743 0x106b28000 + 14147
    23  org.python.python                       0x00000001065a2f72 PyEval_EvalFrameEx + 3557
    24  org.python.python                       0x00000001065a2147 PyEval_EvalCodeEx + 1934
    25  org.python.python                       0x00000001065dbd7a 0x10658b000 + 331130
    26  org.python.python                       0x000000010659a6c6 PyObject_Call + 97
    27  _functools.so                           0x00000001068d34a2 0x1068d2000 + 5282
    28  org.python.python                       0x000000010659a6c6 PyObject_Call + 97
    29  org.python.python                       0x00000001065a478d PyEval_EvalFrameEx + 9728
    30  org.python.python                       0x00000001065a2147 PyEval_EvalCodeEx + 1934
    31  org.python.python                       0x00000001065a88df 0x10658b000 + 121055
    32  org.python.python                       0x00000001065a463a PyEval_EvalFrameEx + 9389
    33  org.python.python                       0x00000001065a2147 PyEval_EvalCodeEx + 1934
    34  org.python.python                       0x00000001065a88df 0x10658b000 + 121055
    35  org.python.python                       0x00000001065a463a PyEval_EvalFrameEx + 9389
    36  org.python.python                       0x00000001065a8869 0x10658b000 + 120937
    37  org.python.python                       0x00000001065a463a PyEval_EvalFrameEx + 9389
    38  org.python.python                       0x00000001065a2147 PyEval_EvalCodeEx + 1934
    39  org.python.python                       0x00000001065a19b3 PyEval_EvalCode + 54
    40  org.python.python                       0x00000001065ddc70 0x10658b000 + 339056
    41  org.python.python                       0x00000001065ddd3c PyRun_FileExFlags + 165
    42  org.python.python                       0x00000001065dd726 PyRun_SimpleFileExFlags + 410
    43  org.python.python                       0x0000000106601e27 Py_Main + 2715
    44  libdyld.dylib                           0x00007fff8fe447e1 start + 1
    Thread 1:: Dispatch queue: com.apple.libsystem_network
    0   libsystem_c.dylib                       0x00007fff87fb32dd tiny_malloc_from_free_list + 453
    1   libsystem_c.dylib                       0x00007fff87fb3ad8 szone_malloc_should_clear + 971
    2   libsystem_c.dylib                       0x00007fff87fa6153 malloc_zone_malloc + 71
    3   libsystem_c.dylib                       0x00007fff87fa6ba7 malloc + 41
    4   libsystem_c.dylib                       0x00007fff8801026d tre_make_trans + 412
    5   libsystem_c.dylib                       0x00007fff8800ff59 tre_ast_to_tnfa + 145
    6   libsystem_c.dylib                       0x00007fff8800ff2f tre_ast_to_tnfa + 103
    7   libsystem_c.dylib                       0x00007fff8800e30b tre_compile + 4627
    8   libsystem_c.dylib                       0x00007fff8800c79f regncomp_l + 346
    9   libsystem_c.dylib                       0x00007fff87f9b278 __asl_parse_time_block_invoke_0 + 151
    10  libdispatch.dylib                       0x00007fff8a6ce0b6 _dispatch_client_callout + 8
    11  libdispatch.dylib                       0x00007fff8a6ce041 dispatch_once_f + 50
    12  libsystem_c.dylib                       0x00007fff87f9ad57 asl_parse_time + 61
    13  libsystem_c.dylib                       0x00007fff87fa139a _asl_time_string + 72
    14  libsystem_c.dylib                       0x00007fff87fa130e asl_msg_to_string_raw + 322
    15  libsystem_c.dylib                       0x00007fff87f99c77 _asl_send_message + 1273
    16  libsystem_c.dylib                       0x00007fff87f99412 _asl_lib_vlog + 513
    17  libsystem_c.dylib                       0x00007fff87f86839 vsyslog + 107
    18  libdispatch.dylib                       0x00007fff8a6d3cd1 _dispatch_log + 224
    19  libdispatch.dylib                       0x00007fff8a6cfba0 _dispatch_update_kq + 430
    20  libdispatch.dylib                       0x00007fff8a6cf9ee _dispatch_mgr_wakeup + 16
    21  libdispatch.dylib                       0x00007fff8a6cee65 _dispatch_wakeup + 28
    22  libdispatch.dylib                       0x00007fff8a6cee10 _dispatch_queue_push_list_slow2 + 33
    23  libdispatch.dylib                       0x00007fff8a6ceecd _dispatch_wakeup + 132
    24  libdispatch.dylib                       0x00007fff8a6cf027 _dispatch_resume_slow + 17
    25  libxpc.dylib                            0x00007fff8ea12ff2 _xpc_connection_listen_for_reply + 198
    26  libxpc.dylib                            0x00007fff8ea13ccf xpc_connection_send_message_with_reply + 122
    27  libsystem_network.dylib                 0x00007fff9163bd8c __net_helper_get_settings_block_invoke_0 + 181
    28  libdispatch.dylib                       0x00007fff8a6d1f01 _dispatch_call_block_and_release + 15
    29  libdispatch.dylib                       0x00007fff8a6ce0b6 _dispatch_client_callout + 8
    30  libdispatch.dylib                       0x00007fff8a6cf47f _dispatch_queue_drain + 235
    31  libdispatch.dylib                       0x00007fff8a6cf2f1 _dispatch_queue_invoke + 52
    32  libdispatch.dylib                       0x00007fff8a6cf1c3 _dispatch_worker_thread2 + 249
    33  libsystem_c.dylib                       0x00007fff87f8fcab _pthread_wqthread + 404
    34  libsystem_c.dylib                       0x00007fff87f7a171 start_wqthread + 13
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff85af06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff87f8feec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff87f8fcb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff87f7a171 start_wqthread + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x00000000000fffe0  rbx: 0x00000000000009ac  rcx: 0x00007faa1b000000  rdx: 0x00007faa1b09ad80
      rdi: 0x0000000106585000  rsi: 0x00000001066fea00  rbp: 0x00007fff5967ced0  rsp: 0x00007fff5967cec8
       r8: 0x000000000000003f   r9: 0x000007faa1b09ad8  r10: 0x00007faa1b0b6300  r11: 0x000000000000fffe
      r12: 0x0000000000000002  r13: 0x00007faa1b09ad60  r14: 0x00000000066efffe  r15: 0x00000001066fea00
      rip: 0x00007fff87fafde1  rfl: 0x0000000000010202  cr2: 0x00007faa1b19ad5e
    Logical CPU: 0
    Binary Images:
           0x106581000 -        0x106581fff  org.python.python (2.7.2 - 2.7.2) <A3CE5618-7FE0-3307-B2C1-DE2661C936B2> /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/C ontents/MacOS/Python
           0x10658b000 -        0x106698fff  org.python.python (2.7.2 - 2.7.2) <B2E5B3C9-2D7C-37D7-B23D-84DEF8DDAF28> /System/Library/Frameworks/Python.framework/Versions/2.7/Python
           0x10689b000 -        0x10689efff  operator.so (60.3) <16E539EB-683E-3BDF-83AA-77ED26146560> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/operator.so
           0x1068d2000 -        0x1068d3fff  _functools.so (60.3) <610F4A5F-CEE5-3353-94CD-F586D4F2DAD0> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_functools.so
           0x1068d7000 -        0x1068d8fff  _locale.so (60.3) <D7B03EB6-5126-3306-8699-D3816B044AAB> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_locale.so
           0x1068dc000 -        0x1068ddfff  time.so (60.3) <B81E8A2D-38E3-3BA7-AA2F-7A543F20DACF> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/time.so
           0x106924000 -        0x106926fff  select.so (60.3) <191F03CF-4038-38AF-A0BA-22AC770298A0> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/select.so
           0x10692c000 -        0x10692dfff  fcntl.so (60.3) <5E2DBA68-27EB-3589-B7B4-8B7918DC9716> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/fcntl.so
           0x106931000 -        0x106934fff  _struct.so (60.3) <2D1A807F-2084-3CEE-9E4B-DE124502AB69> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_struct.so
           0x10693a000 -        0x10693cfff  binascii.so (60.3) <A96BD9F2-1025-3803-A942-AC8AE48243A9> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/binascii.so
           0x106940000 -        0x106941fff  cStringIO.so (60.3) <F4174A1F-B66E-3986-985C-0632FCD266F9> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/cStringIO.so
           0x106946000 -        0x106949fff  _collections.so (60.3) <20EAC750-00E1-3216-BB1F-472C0CEA6118> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_collections.so
           0x10698f000 -        0x106995fff  itertools.so (60.3) <C273B16D-A69E-3D3C-B3F5-43F6B0BC333F> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/itertools.so
           0x10699e000 -        0x10699efff  _bisect.so (60.3) <BEAA36C6-86EF-3272-9F95-29AED2B60109> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_bisect.so
           0x1069a2000 -        0x1069a3fff  _heapq.so (60.3) <C02D109C-B83B-385E-86E9-04F551749448> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_heapq.so
           0x1069a8000 -        0x1069b3ff7  datetime.so (60.3) <B359E7F5-D6D1-343C-A770-F1186D123691> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/datetime.so
           0x1069bc000 -        0x1069c5fff  _sqlite3.so (60.3) <C0006BFF-3590-3B8E-A9B5-DECD4A764236> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_sqlite3.so
           0x106acf000 -        0x106ad3fff  math.so (60.3) <15868E58-734E-3A35-A4C2-AC4625F37902> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/math.so
           0x106b19000 -        0x106b1afff  _hashlib.so (60.3) <9B8C96E2-6DE6-3830-B300-35C790DA40C7> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_hashlib.so
           0x106b1f000 -        0x106b22fff  strop.so (60.3) <33FECDE8-3D85-37A8-95CA-08C1F2B820D4> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/strop.so
           0x106b28000 -        0x106b2eff7  _socket.so (60.3) <E186283B-C7D4-3D7E-9198-CD7761B70100> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_socket.so
           0x106b36000 -        0x106b39fff  _ssl.so (60.3) <2AEDA15A-56F4-3E82-9415-297BFE6C8F38> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_ssl.so
           0x106b7f000 -        0x106b7ffff  _scproxy.so (60.3) <43CCA6F3-BA7C-3186-8450-B63D00D8AC6F> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_scproxy.so
           0x106bc4000 -        0x106bc8fff  array.so (60.3) <56A0FB1F-7603-3450-AF31-9801D9AB95D5> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/array.so
           0x106bce000 -        0x106bcffff  _random.so (60.3) <E2D3E74F-9797-30D4-A9B7-E9FE72564C50> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_random.so
           0x106bd3000 -        0x106bdffff  cPickle.so (60.3) <869D9434-2C00-3EC8-93A1-2A8104957B7E> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/cPickle.so
           0x106c25000 -        0x106c29fff  _json.so (60.3) <5899CF83-4D57-34C0-A01F-DC215C5C26D0> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_json.so
           0x106cae000 -        0x106cbffff  _io.so (60.3) <79CDBE7E-1D18-39A6-99AA-CA9466FAD6C2> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_io.so
           0x106d4e000 -        0x106d4efff  grp.so (60.3) <F1C42F13-D323-3F5A-B59E-ACB09DD18ABE> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/grp.so
           0x106fd2000 -        0x106fd4fff  zlib.so (60.3) <987E51DB-7827-3F1A-AD5E-CF58C673E644> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/zlib.so
           0x106fd9000 -        0x106fdffff  pyexpat.so (60.3) <72D45F21-63F8-3EEF-B71D-DC73B0309D55> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/pyexpat.so
           0x107066000 -        0x107077fff  _ctypes.so (60.3) <A4E934BA-B8B3-3CD6-9AA6-78458DEAA491> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/_ctypes.so
           0x10740e000 -        0x1074b2ff7  unicodedata.so (60.3) <D2954B53-CE7D-3182-8056-F04F7CAABC6C> /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynl oad/unicodedata.so
        0x7fff66181000 -     0x7fff661b593f  dyld (210.2.3) <A40597AA-5529-3337-8C09-D8A014EB1578> /usr/lib/dyld
        0x7fff84fa3000 -     0x7fff8518cfff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff851b6000 -     0x7fff853b6fff  libicucore.A.dylib (491.11.1) <CC318A27-878A-38CE-9292-1B98353FA9C7> /usr/lib/libicucore.A.dylib
        0x7fff85724000 -     0x7fff85729fff  libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
        0x7fff85ade000 -     0x7fff85af9ff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff85dc3000 -     0x7fff85dcefff  libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
        0x7fff861ed000 -     0x7fff861eeff7  libSystem.B.dylib (169.3) <365477AB-D641-389D-B8F4-A1FAE9657EEE> /usr/lib/libSystem.B.dylib
        0x7fff86617000 -     0x7fff86625fff  libcommonCrypto.dylib (60026) <2D6537F5-1B5E-305C-A1CF-D1FA80CA3939> /usr/lib/system/libcommonCrypto.dylib
        0x7fff87f30000 -     0x7fff87f38fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff87f79000 -     0x7fff88045fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff88046000 -     0x7fff88058ff7  libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
        0x7fff88134000 -     0x7fff88159ff7  libc++abi.dylib (24.4) <E7BD9363-1D25-3551-A68A-2E2FF6ABECD7> /usr/lib/libc++abi.dylib
        0x7fff88221000 -     0x7fff88272ff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <E095637C-457F-3D8F-AE32-A032F9D5A46C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
        0x7fff8835f000 -     0x7fff8838dff7  libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
        0x7fff89823000 -     0x7fff8982bff7  libsystem_dnssd.dylib (379.32.1) <62AA0B84-188A-348B-8F9E-3E2DB08DB93C> /usr/lib/system/libsystem_dnssd.dylib
        0x7fff89f9d000 -     0x7fff8a09afff  libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
        0x7fff8a6cc000 -     0x7fff8a6e1ff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8a704000 -     0x7fff8a750ff7  libauto.dylib (185.1) <73CDC482-16E3-3FC7-9BB4-FBA2DA44DBC2> /usr/lib/libauto.dylib
        0x7fff8ac23000 -     0x7fff8ac24fff  libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
        0x7fff8acf1000 -     0x7fff8adf3fff  libcrypto.0.9.8.dylib (47) <74F165AD-4572-3B26-B0E2-A97477FE59D0> /usr/lib/libcrypto.0.9.8.dylib
        0x7fff8aeea000 -     0x7fff8b00292f  libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
        0x7fff8b070000 -     0x7fff8b072fff  com.apple.TrustEvaluationAgent (2.0 - 23) <A97D348B-32BF-3E52-8DF2-59BFAD21E1A3> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
        0x7fff8b112000 -     0x7fff8b113ff7  libsystem_sandbox.dylib (220) <3C3B03CF-C525-3CB3-8557-62E91B93AC95> /usr/lib/system/libsystem_sandbox.dylib
        0x7fff8ba1a000 -     0x7fff8ba1bff7  libdnsinfo.dylib (453.18) <E7595861-ECF9-336E-9901-BED2620FAA80> /usr/lib/system/libdnsinfo.dylib
        0x7fff8bbfa000 -     0x7fff8bc62ff7  libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
        0x7fff8c0fb000 -     0x7fff8c132ff7  libssl.0.9.8.dylib (47) <923945E6-C489-3406-903B-A362410753F8> /usr/lib/libssl.0.9.8.dylib
        0x7fff8cd20000 -     0x7fff8cd56fff  libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
        0x7fff8d244000 -     0x7fff8d249fff  libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
        0x7fff8ea07000 -     0x7fff8ea29ff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
        0x7fff8eadd000 -     0x7fff8eb2cff7  libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib
        0x7fff8eb55000 -     0x7fff8eb57fff  libquarantine.dylib (52) <4BE2E642-A14F-340A-B482-5BD2AEFD9C24> /usr/lib/system/libquarantine.dylib
        0x7fff8f0ec000 -     0x7fff8f0f2fff  libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
        0x7fff8fe42000 -     0x7fff8fe45ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8fe93000 -     0x7fff8fe95ff7  libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
        0x7fff8fe96000 -     0x7fff8fe9dfff  libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
        0x7fff9022f000 -     0x7fff90230fff  libffi.dylib (18) <D20FE81C-271C-3446-ABC8-50B6A6F5BEA4> /usr/lib/libffi.dylib
        0x7fff904f0000 -     0x7fff9050bff7  libexpat.1.dylib (12) <95D59F1F-0A5C-3F33-BA97-26F7D796CE7A> /usr/lib/libexpat.1.dylib
        0x7fff908e2000 -     0x7fff908e3fff  libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
        0x7fff90c13000 -     0x7fff90c14ff7  libremovefile.dylib (23.1) <DBBFAF35-AC78-3856-92F6-6E4FD9DF14A2> /usr/lib/system/libremovefile.dylib
        0x7fff912c0000 -     0x7fff912c6ff7  libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
        0x7fff91562000 -     0x7fff915cbfff  libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
        0x7fff915cc000 -     0x7fff915ccfff  libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
        0x7fff91635000 -     0x7fff91643ff7  libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
    External Modification Summary:
      Calls made by other processes targeting this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by all processes on this machine:
        task_for_pid: 5843
        thread_create: 1
        thread_set_state: 0
    VM Region Summary:
    ReadOnly portion of Libraries: Total=67.5M resident=24.5M(36%) swapped_out_or_unallocated=43.0M(64%)
    Writable regions: Total=66.6M written=11.4M(17%) resident=19.8M(30%) swapped_out=0K(0%) unallocated=46.8M(70%)
    REGION TYPE                      VIRTUAL
    ===========                      =======
    MALLOC                             55.5M
    MALLOC guard page                    32K
    STACK GUARD                        56.0M
    Stack                              10.6M
    VM_ALLOCATE                          20K
    __DATA                             1924K
    __LINKEDIT                         53.6M
    __TEXT                             13.9M
    __UNICODE                           544K
    shared memory                        12K
    ===========                      =======
    TOTAL                             192.0M
    Model: MacBookAir4,2, BootROM MBA41.0077.B0F, 2 processors, Intel Core i7, 1.8 GHz, 4 GB, SMC 1.73f65
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 384 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020
    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80AD, 0x484D54333235533642465238432D48392020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (5.106.98.81.22)
    Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en0
    Serial ATA Device: APPLE SSD SM256C, 251 GB
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfd100000 / 2
    USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8404, 0xfd110000 / 3
    USB Device: FaceTime Camera (Built-in), apple_vendor_id, 0x850a, 0xfa200000 / 3
    USB Device: hub_device, 0x0424  (SMSC), 0x2513, 0xfa100000 / 2
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x024c, 0xfa120000 / 5
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821f, 0xfa113000 / 8

    I guess you could say Cheetah is in stable release since 2010 as that was when it was last updated. Python has changed considerably since then.
    Pypl.org shows a list of available packages by ascending Python version. By the time one looks for Cheetah support in Python 2.6, it is strictly Linux. In the Python 2.7 section, there is no Cheetah package listed at all.
    In my estimation, development on Cheetah has been abandoned, and it remains incompatible with Python 2.7.2 as installed on OS X. You should abandon Cheetah. Look at Jinja2, or Django.
    OS X still uses Python scripts for some system activity. If the system version of Python gets messed up with an incompatible module, these system python scripts are compromised too.
    Seriously, look at Pythonbrew. It allows you to create full-blown Python installs and switch between versions and virtual environments.

Maybe you are looking for

  • Interest Rate

    Dear All , I want to calculate the interest with dunning. But i do no understand the interest rate logic with dunning . I need a calculation as below example . Is it possible ? for example , Invoice = 1000 EUR Net due date =12.03.2007 Interest Rate S

  • How can I display a range of dates on my calendar

    I have a table with the following fields: beginning date, end date, person name and color. I will like to change the background color for each person range of days to the color assign to each person.

  • How can I smooth out the pixelation of my drawing?

    I'm trying to create a line drawing effect similar to image 1 below .I have studied numerous you tube videos but my images end up looking to pixilated (see image 2). Image 1 has more of a that line drawn look of a pen tool. I would like to be able to

  • IPhone synced with another library..."Erase and Sync" question

    I helped someone transfer from an older iPhone to an iPhone 6 and did an encrypted backup on my laptop and then restored that backup to their new phone. When they took the phone home and tried to sync their library with it they got the following mess

  • Merging of two company codes.

    Dear SAP consultants,                                   At present there are two company codes ( lets say 1000 and 2000 ) which have different plants assigned to them. Now company code 1000 is merging into company code 2000. Please guide me what are