Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sudden Termination of Python when importing pinocchio.casadi #1578

Closed
ghost opened this issue Dec 20, 2021 · 6 comments
Closed

Sudden Termination of Python when importing pinocchio.casadi #1578

ghost opened this issue Dec 20, 2021 · 6 comments

Comments

@ghost
Copy link

ghost commented Dec 20, 2021

The Import failed without any message and python just exit. I can still compile c++ codes with pinocchio. What should I do to debug? It still works days ago.

@ghost
Copy link
Author

ghost commented Dec 20, 2021

pinocchio can be normally imported. only pinocchio.casadi is unavailable

@jcarpent
Copy link
Contributor

On which commit are you working now? What was the former one?

@ghost
Copy link
Author

ghost commented Dec 20, 2021

I debugged for a while and found that when import pinocchio.casadi a SX is created with value a tuple (0), which may caused exception. I guess it may use import casadi.casadi instead of import casadi
The casadi version is 3.5. Can you debug see if this happens on your pc? the exception code is about line 9234 in casadi.py in casadi folder, see if the args of init is a tuple zero
Traceback
Wrong number or type of arguments for overloaded function 'transpose'.
Possible prototypes are:
transpose(Sparsity)
transpose(DM)
transpose(SX)
transpose(MX)
You have: '(SX)'

@jcarpent
Copy link
Contributor

Sorry, but you are hard to follow.
Could you provide a tiny example that is not working on your side in such a way we can try on our side?

@ghost
Copy link
Author

ghost commented Dec 20, 2021

Just import pinocchio.casadi. I see Process finished with exit code -1073741819 (0xC0000005)
image
and it comes to
image
after line 9238 is excuted, it exits directly

@jcarpent
Copy link
Contributor

I'm using casadi 3.5.5 and everything works perfectly well.
If it was working well a few days ago, it should remain the case. I suspect some change on your side.

Please consider reinstalling a clean version in a clean environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant