[Haifux] Suggested lecture: Crash and burn: writing Linux application fault handlers
Howdy folks, I'd like to suggest a lecture for Haifux meeting. Title: Crash and burn: writing Linux application fault handlers Abstract: Complementing the standard Linux fault handler (Segmentation fault. Core dumped.) with a custom handler that reports the crashing program state without a debugger is a useful endeavor in many situations. Unfortunately, writing such a fault handler correctly can be surprisingly hard and requires certain amount of black magic. The proposed lecture is a tutorial that will demonstrate how to write such a handler, covering such topics as: getting program symbolic stack trace and registers and reporting them safely, the care and feeding of async signal POSIX handler functions, how to avoid implicit memory allocations and how to test for them, how to handle multi-threaded faults, the black magic involved with how Linux handles signal handlers, the unfortunate effect this has on obtaining a correct stack trace in case of a fault and how to overcome this limitation. Let me know if there is interest and available times. Cheers, Gilad -- Gilad Ben-Yossef Chief Coffee Drinker Codefidence Ltd. The code is free, your time isn't.(TM) Web: http://codefidence.com Email: [EMAIL PROTECTED] Office: +972-8-9316883 ext. 201 Fax: +972-8-9316885 Mobile: +972-52-8260388 ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
Re: [Haifux] Suggested lecture: Crash and burn: writing Linux application fault handlers
On Mon, May 12, 2008 at 10:48 AM, Gilad Ben-Yossef [EMAIL PROTECTED] wrote: Howdy folks, I'd like to suggest a lecture for Haifux meeting. Title: Crash and burn: writing Linux application fault handlers Abstract: Complementing the standard Linux fault handler (Segmentation fault. Core dumped.) with a custom handler that reports the crashing program state without a debugger is a useful endeavor in many situations. Unfortunately, writing such a fault handler correctly can be surprisingly hard and requires certain amount of black magic. The proposed lecture is a tutorial that will demonstrate how to write such a handler, covering such topics as: getting program symbolic stack trace and registers and reporting them safely, the care and feeding of async signal POSIX handler functions, how to avoid implicit memory allocations and how to test for them, how to handle multi-threaded faults, the black magic involved with how Linux handles signal handlers, the unfortunate effect this has on obtaining a correct stack trace in case of a fault and how to overcome this limitation. Let me know if there is interest and available times. I'm voting for yes!! with both hands! Cheers, Gilad -- Gilad Ben-Yossef Chief Coffee Drinker Codefidence Ltd. The code is free, your time isn't.(TM) Web: http://codefidence.com Email: [EMAIL PROTECTED] Office: +972-8-9316883 ext. 201 Fax: +972-8-9316885 Mobile: +972-52-8260388 ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux -- Zaar ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
Re: [Haifux] Suggested lecture: Crash and burn: writing Linux application fault handlers
This goes under why bother asking, just schedule it! Eli Gilad Ben-Yossef wrote: Howdy folks, I'd like to suggest a lecture for Haifux meeting. Title: Crash and burn: writing Linux application fault handlers ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
Re: [Haifux] Suggested lecture: Crash and burn: writing Linux application fault handlers
Sure, schedule it. Howdy folks, I'd like to suggest a lecture for Haifux meeting. Title: Crash and burn: writing Linux application fault handlers Abstract: Complementing the standard Linux fault handler (Segmentation fault. Core dumped.) with a custom handler that reports the crashing program state without a debugger is a useful endeavor in many situations. Unfortunately, writing such a fault handler correctly can be surprisingly hard and requires certain amount of black magic. The proposed lecture is a tutorial that will demonstrate how to write such a handler, covering such topics as: getting program symbolic stack trace and registers and reporting them safely, the care and feeding of async signal POSIX handler functions, how to avoid implicit memory allocations and how to test for them, how to handle multi-threaded faults, the black magic involved with how Linux handles signal handlers, the unfortunate effect this has on obtaining a correct stack trace in case of a fault and how to overcome this limitation. Let me know if there is interest and available times. Cheers, Gilad -- Gilad Ben-Yossef Chief Coffee Drinker Codefidence Ltd. The code is free, your time isn't.(TM) Web: http://codefidence.com Email: [EMAIL PROTECTED] Office: +972-8-9316883 ext. 201 Fax: +972-8-9316885 Mobile: +972-52-8260388 ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux -- Change is inevitable; progress is optional. ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
Re: [Haifux] Suggested lecture: Crash and burn: writing Linux application fault handlers
I am interested. Gabi -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gilad Ben-Yossef Sent: Monday, May 12, 2008 10:48 AM To: haifux@haifux.org Subject: [Haifux] Suggested lecture: Crash and burn: writing Linux application fault handlers Howdy folks, I'd like to suggest a lecture for Haifux meeting. Title: Crash and burn: writing Linux application fault handlers Abstract: Complementing the standard Linux fault handler (Segmentation fault. Core dumped.) with a custom handler that reports the crashing program state without a debugger is a useful endeavor in many situations. Unfortunately, writing such a fault handler correctly can be surprisingly hard and requires certain amount of black magic. The proposed lecture is a tutorial that will demonstrate how to write such a handler, covering such topics as: getting program symbolic stack trace and registers and reporting them safely, the care and feeding of async signal POSIX handler functions, how to avoid implicit memory allocations and how to test for them, how to handle multi-threaded faults, the black magic involved with how Linux handles signal handlers, the unfortunate effect this has on obtaining a correct stack trace in case of a fault and how to overcome this limitation. Let me know if there is interest and available times. Cheers, Gilad -- Gilad Ben-Yossef Chief Coffee Drinker Codefidence Ltd. The code is free, your time isn't.(TM) Web: http://codefidence.com Email: [EMAIL PROTECTED] Office: +972-8-9316883 ext. 201 Fax: +972-8-9316885 Mobile: +972-52-8260388 ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux ___ Haifux mailing list Haifux@haifux.org http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
