On Aug 30, 6:57 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 8/30/07, David Joyner <[EMAIL PROTECTED]> wrote:
>
>
>
> > > On a suse 101. amd64: SAGE compiled file. The sage -testall
> > revealed several seg faults, such as:
>
> > sage -t matrix/strassen.pyx
>
> > ------------------------------------------------------------
> > Unhandled SIGSEGV: A segmentation fault occured in SAGE.
> > This probably occured because a *compiled* component
> > of SAGE has a bug in it (typically accessing invalid memory)
> > or is not properly wrapped with _sig_on, _sig_off.
> > You might want to run SAGE under gdb with 'sage -gdb' to debug this.
> > SAGE will now terminate (sorry).
> > ------------------------------------------------------------
> > A mysterious error (perphaps a memory error?) occured, which may have
> > crashed doctest.
>
> > (BTW, "occured" is spelled wrong I think.)
>
> Thanks, I've fixed the spelling mistakes.
>
> The above crash looks pretty serious -- it's evidently a 64-bit only issue,
> which was probably introduced by our work to fix other bugs (??) and/or
> memory leaks. This will be a blocker that has to be fixed before sage-2.8.3
> can be released.
>
The only thing we touched was the de-initialization of the tables in
m4ri, and I saw some potential issue in there with int* pointers:
void buildAllCodes() {
int k;
codebook=calloc(MAXKAY+1, sizeof(code *)); [line
85]
for(k=1 ; k<MAXKAY+1; k++) {
codebook[k] = (code *)calloc(sizeof(code),1); [line
88]
codebook[k]->ord =(int *)calloc(TWOPOW(k),sizeof(int)); [line
89]
codebook[k]->inc =(int *)calloc(TWOPOW(k),sizeof(int)); [line
90]
buildCodeFlex(codebook[k]->ord, codebook[k]->inc, k);
}
}
> > sage -t tut.tex
>
> > even though it said "All tests passed!" for that section.
>
That bug might have been there for a long time.
> If one does "sage -testall" it also tests tut.tex and const.tex, I
> think, which is
> useful. The main thing I want though is the output of "make test".
>
> William
Lets wait for some backtraces before jumping to conclusion.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
