On Wed, Feb 2, 2011 at 14:08, Sri Ram Vemulpali <sri.ram.gmu06@xxxxxxxxx> wrote: > Hi all, > > I know that when a thread in an application do invalid memory > reference, OS generates SIGSEGV(segmentation fault) signal and > terminates application. What if we handle this signal by defining a > signal handler to perform to terminate only the thread did invalid > memory reference. So, that the application will not be terminated. > Also, is there any way, we can find when SIGSEGV is generated to get > the invalid memory reference and thread id, who caused this fault. I > know debuggers are written in such fashion. Can anyone point me to > right direction. Thanks in advance. Perhaps phrack article in issue 58 file 03 could help you :) In case you're lazy, here's the URL: http://www.phrack.org/issues.html?issue=58&id=3#article look for the section: "Subject: Getting rid of SIGSEGV - for fun but not for profit." A bit hackish, but I think it is worth to read. Enjoy :) -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
