-
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
getting corrupted double-linked list #634
Comments
It seems to have to do with |
Unfortunately the 'fix' reintroduces a memory leak I need to get to grips
with.
…On Tue, Nov 26, 2024 at 9:41 AM Jos De Roo ***@***.***> wrote:
It seems to have to do with format/2 and things are back OK in
https://github.com/eyereasoner/eye3/tree/v1.2.1
—
Reply to this email directly, view it on GitHub
<#634 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFNKSEQVOEMTY6DG7XSENUL2COYUJAVCNFSM6AAAAABSO7DG2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJZGI2TOMBSGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
By the way, this didn't give an error for me...
whereas running ./test did. |
But valgrind shows somethings up...
|
Good to see that and it is back OK for eye3 v1.2.1
|
So you removed format and it's good now? |
It is! |
Not sure if this is helpful, but another snippet that triggers a similar invalid read: :- use_module(library(clpz)).
test(X) :-
Y mod 100 #= 0,
X #= Y.
|
Also...
|
I found that running turning on trace on the one I posted explodes partway through with some corrupted pointers, might be a hint:
|
Introduced problem elsewhere it seems. |
I'm going with this fix. It just introduces a single small memory leak on initialization goals. I'll look into it again tomorrow. |
Thanks, it looks better now for sure. Trace thing still happens but maybe unrelated. |
We are getting a
corrupted double-linked list
:It also occurs in 7 of our other examples and test cases:
The text was updated successfully, but these errors were encountered: