John Voight wrote: > Hello all-- >
Hello John, > I got the following message today: > > ------------------------------------------------------------ > 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). > ------------------------------------------------------------ > > Just to check: Do I need to _sig_on and _sig_off inside my Cython > code? So this is your own Cython code and not Sage's? If so what does gdb say when you run the seesion under it and do a backtrace? > Or do I have a memory leak on my hands? That is unlikely to be the cause. > I would be a little > surprised if it is the latter, since it only shows up after a > significant length of time in the algorithm, but anything is > possible... > If you can post the code as well as an example that makes the code segfault I can take a look. It would also be interesting to know if this only happens on certain platforms or compilers. If you didn't test just let us know the details where you saw the problem. > Wish I could be part of the bug squash on Thursday, I'll be up in > Montreal that day! > Well, with probability 1 there will be another one :) > Yours, > > John Voight Cheers, Michael > Assistant Professor of Mathematics > University of Vermont > [EMAIL PROTECTED] > [EMAIL PROTECTED] > http://www.cems.uvm.edu/~voight/ --~--~---------~--~----~------------~-------~--~----~ 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/ -~----------~----~----~----~------~----~------~--~---
