Skip to content

_macosx.so crash in build using Xcode 5 #2451

Closed

Description

@fonnesbeck

After upgrading to Xcode 5 on OS X 10.8.4, matplotlib is no longer able to use the macosx backend without crashing.

Here is the crash report from one such crash.

This is a build for the ScipySuperpack, so I am using a script that has successfully built working packages every 2 weeks or so until now. I also tried using the instructions in README.osx, with the same result.

Activity

  1. dmcdougall commented on Sep 23, 2013

    @dmcdougall
    Member

    Looks like you're building from master. Are you able to successfully build v1.3 with Xcode 5?

  2. fonnesbeck commented on Sep 23, 2013

    @fonnesbeck
    Author

    I get a different error when running a build of 1.3:

    ImportError: cannot import name _string_to_bool
    

    This occurs when pylab is imported.

  3. fonnesbeck commented on Sep 23, 2013

    @fonnesbeck
    Author

    OK, I got a build to work using the 1.3 release. No crash.

  4. dmcdougall commented on Sep 23, 2013

    @dmcdougall
    Member

    Thanks for the diagnostic information. This is probably related to the migration from 2to3 to six (the relevant commit is f4adec7), but I could be wrong. As a test, would you mind seeing if you are able to successfully build with Xcode 5 using the patch in #2433? If so, I'll close this issue. If not, then that means there's something funky going on.

  5. fonnesbeck commented on Sep 24, 2013

    @fonnesbeck
    Author

    This patch does not fix the issue. Same behavior results.

  6. mdboom commented on Sep 24, 2013

    @mdboom
    Member

    Can you provide a full script that reproduces the error? (Or point to one of our examples that fails?) I'm unable to reproduce (once #2433 is applied, now merged to master).

  7. fonnesbeck commented on Sep 24, 2013

    @fonnesbeck
    Author

    Any plotting will cause the failure. This does it for me every time:

    import matplotlib.pyplot as plt
    plt.plot(range(10))
    

    If I roll back to the 1.3 release, the problem disappears. I will try again from master incase I made a mistake in testing the patch.

  8. mdboom commented on Sep 30, 2013

    @mdboom
    Member

    Make sure you remove the build directory before rebuilding to ensure a complete rebuild of the C++ code.

  9. fonnesbeck commented on Sep 30, 2013

    @fonnesbeck
    Author

    This is automated in my build script, so that is not the issue.

  10. tacaswell commented on Aug 17, 2014

    @tacaswell
    Member

    @fonnesbeck Is this still an issue?

    @matthew-brett Do you build with a version of xcode?

  11. added this to the v1.4.x milestone on Aug 17, 2014
  12. matthew-brett commented on Aug 21, 2014

    @matthew-brett
    Contributor

    Yes - I build with the latest xcode - so I guess this isn't an issue.
    The build logs from matplotlib-wheels give the full output if anyone
    wants to check.

  13. tacaswell commented on Aug 21, 2014

    @tacaswell
    Member

    I am going to close this then.

    @fonnesbeck ping to have this re-opened if you still have issues.

  14. pelson commented on Sep 30, 2014

    @pelson
    Member

    FWIW, whenever I get this, it is because I have old .pyc files in my source checkout. We moved axes.py to axes/__init__.py and any lingering pyc files can get really messed up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions