I would like an option to pike that dumps a pike backtrace on SIGINT as well. (Or as default behaviour.)
An option or environment setting to enable it for any signal would be nice, but I definitely don't think it should be the default for SIGINT.
Can Pike backtraces be dumped on SIGSEGV?
Yes, why not?
How will the security mechanism around that look like?
You mean wrt the pike security system, or security in general, e.g. concerns about a user segfaulting a process to get access to sensitive data on the stack? I think the last part should be solved by self-sensoring string objects, which were discussed a while back.
Turn of catching SIGSEGV in the SIGSEGV handler?
It's probably good to be able to disable it from inside pike.
o Implement this_function().
Is this tricky?
Not at all.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-10-02 17:22: Subject: Some tasks from the conference
o Dump pike backtraces on SIGSEGV.
I would like an option to pike that dumps a pike backtrace on SIGINT as well. (Or as default behaviour.)
Can Pike backtraces be dumped on SIGSEGV? How wiill the security mechanism around that look like? Turn of catching SIGSEGV in the SIGSEGV handler?
(Speaking of which, maybe SIGQUIT should be trapped by Hilfe to reset the terminal?)
o Finish the implementation of the "variant" feature (i.e. runtime dispatch on function argument types).
Can someone elaborate on this?
o Fix LXR view of the pike source on the pike site.
LXR?
o Implement this_function().
Is this tricky?
/ Mirar