-
Notifications
You must be signed in to change notification settings - Fork 13
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
Circuit_Get_Losses
segfaults
#114
Comments
Which branch/commit are you using? |
Yep. See also #56 |
If you're using the master branch and 0.12 beta releases, please provide the sequence of calls so I can try to reproduce. If it's 0.10.x, avoid opening new issues for that. Although there are a few more places that need state checks (per #56), half of the code has been rewritten since 0.10.x. Worst case scenario, link to the debug version of DSS C-API and you should get detailed info -- either started through a debugger like GDB or load the core dump afterwards. Some general info at https://github.com/dss-extensions/dss_capi/blob/master/docs/debug.md |
I'm using the master branch, here is the sequence of calls I make:
|
hm... seems fine. Are you initializing the two pointers for that function?
I noticed you're not checking for DSS errors. Check |
Figured it out - the issue was that I was not properly initializing the pointers passed to the function. |
I have the following Rust binding to the
Circuit_Get_Losses
function. Calling it produces a segmentation fault and core dump.output:
I'm assuming there's some state initialization that I haven't done, but I'm unsure what needs to be initialized.
The text was updated successfully, but these errors were encountered: