-
-
Notifications
You must be signed in to change notification settings - Fork 478
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
Giac consistent segfault in giac::zmakelinesplit on macos M2 #38864
Comments
I need to reproduce that with giac natively. I understand it's a call to gbasis with katsura 9 (but maybe with katsura10, katsura indexation is not always consistent) |
|
And in the debugger
|
Thanks for the detailled information. The lldb session would be more interesting if giac was compiled with debug infos, it should be possible to see the precise line where the segfault happens, and examine variables. I'll do that when I'll have access to a Mac, should be on Tuesday November 5th or Wednesday 6th. |
Compiled with debug symbols:
|
It seems your source code is not synchronized with mine, so it's hard to find some useful information here, most probably the x variable refers to a non existent address, and the y variable itself is suspect (dimension 0). Moreover since there are optimizations in the data structure, printing variables is not very informative for the type of x and y. I have a gdb macro in my .gdbinit file
if it applies to lldb as well, then you can type v varname instead of p varname. Otherwise p varname.dbgprint() will display a monomial power in a more informative way. |
Steps To Reproduce
Build Sage on macos M2
Expected Behavior
Testsuite should succeed
Actual Behavior
There are a few giac-related segfaults, for example this one in
void giac::zmakelinesplit<giac::tdeg_t14>(giac::zpolymod<giac::tdeg_t14> const&, giac::tdeg_t14 const*, std::__1::vector<giac::tdeg_t14, std::__1::allocator<giac::tdeg_t14> > const&, void*, std::__1::vector<int, std::__1::allocator<int> > const&, std::__1::vector<unsigned short, std::__1::allocator<unsigned short> >&, std::__1::vector<unsigned short, std::__1::allocator<unsigned short> >*, int)
:Additional Information
For lack of an upstream bug tracker, will use this one to track the issue
Environment
Checklist
The text was updated successfully, but these errors were encountered: