This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Segfault while unwinding an invalid function pointer


> You could, but you shouldn't.  I agree with Jakub: we don't want to be
> messing with signal handlers.  For example, an application is perfectly
> entitled to enable/disable SIGSEGV handlers whenever it wants.

That would likely still work even with trampoline, but ok.
> 
> This seems to me like the cure is worse than the disease.

Then you should document somewhere that the unwinder is racy in this
regard.

-Andi


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]