Hallo! Is there a way to safely catch a SIGSEGV signal? I mean, recovering the read/write error "bypassing" the bad code instruction? In alternative: is there a way, for a user process perspective, to understand if a pointer points to an heap address space or to a stack/anything other address space? thank you! Emilio -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
