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.

Sign up for GitHub

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

Jump to bottom

GetIpoptCurrentViolations segfaults when called before solve #644

Closed
Robbybp opened this issue Feb 13, 2023 · 0 comments · Fixed by #645
Closed

GetIpoptCurrentViolations segfaults when called before solve #644

Robbybp opened this issue Feb 13, 2023 · 0 comments · Fixed by #645

Comments

@Robbybp
Copy link
Contributor

Robbybp commented Feb 13, 2023

I'm using the C interface, and get segfaults when GetIpoptCurrentIterate and GetIpoptCurrentViolations are called before (or after) IpoptSolve. I think it would be nicer to simply return false. The segfaults appear to be because ipopt_problem->tnlp is accessed when it is NULL or undefined.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check whether tnlp is null in GetIpoptCurrentIterate Robbybp/Ipopt
1 participant
@Robbybp