25 May
2018
25 May
'18
7:50 a.m.
2018-05-25 11:06 GMT+02:00 Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum 10353@lyskom.lysator.liu.se:
The latter. Basically, there is no legitimate reason for pike code to trap these signals since there should be nothing pike code can do that cause these signals to be fired.
Right. But when I include some library which corrupts memory into Pike build or make changes to Pike sourcecode itself, then it is possible to crash Pike and then trapping SIGSEGV can bring in additional information about probable place where the memory corruption occurred. Is my understanding correct?