I think it would be very useful to get more information out of a segfault
while Sage is running. To this end I've extended the crash handler
("Unhandled SIGSEGV: A segmentation fault occurred in Sage...") to attach
gdb and extract more information. With these changes you'd get Python or
Cython source level listing and not just a C level backtrace. Patches are
at #13889 + #13881. I think this would make bugreports from non-technical
users much more useful. A review would be appreciated ;-)
An example automatted stack trace is here:
http://trac.sagemath.org/sage_trac/attachment/ticket/13889/sage_crash_wKcUKj.log
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
