-
Notifications
You must be signed in to change notification settings - Fork 161
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
Forbid installing an operation as method for itself, as that leads to crashes #4544
Forbid installing an operation as method for itself, as that leads to crashes #4544
Conversation
The problem is that irredsol 1.4.2 does not actually contain the fix; I made a corresponding comment at bh11/irredsol#12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this change will be needed for the tests to pass (eventually).
1038f01
to
4ba795c
Compare
From a quick look at the code, it seems that irredsol 1.4.3 has the right fix, so hopefully this can be merged soon. |
Triggering such a "method" would lead to a segfault due to a stack overflow. Of course one can still trigger this by e.g. having two operations `foo` and `bar, and installing `foo` as method for `bar` and vice-versa. But that is far less likely to happen by accident. Also, it seems better to fix at least some instances of this issue than to give up because we can't fix it completely.
4ba795c
to
c403e1b
Compare
@alex-konovalov to make progress with this, we need irredsol 1.4.3 in the package distribution. But https://github.com/gap-system/gap/wiki/Package-updates-status was last updated in May... |
Done - they were as on 2nd June, now as of today. Updated tables of contents at https://github.com/gap-system/gap-distribution/releases/tag/package-archives and https://github.com/gap-system/gap/wiki/Package-updates-status |
Seems like CI tests are passing, except for some unrelated quirks. |
Triggering such a "method" would lead to a segfault due to a stack overflow.
Of course one can still trigger this by e.g. having two operations
foo
andbar
, and installingfoo
as method forbar
and vice-versa. But that is farless likely to happen by accident. Also, it seems better to fix at least some
instances of this issue than to give up because we can't fix it completely.
(This used to be PR #4349 but I accidentally deleted the underlying branch, it seems, so I had to reopen it in a fresh PR)