際際滷shows by User: samgwydir / http://www.slideshare.net/images/logo.gif 際際滷shows by User: samgwydir / Sat, 25 Mar 2017 15:21:55 GMT 際際滷Share feed for 際際滷shows by User: samgwydir The History and Future of Core Dumps in FreeBSD /slideshow/the-history-and-future-of-core-dumps-in-freebsd/73634626 freebsd-coredump-history-slides-170325152155
Crash dumps, also known as core dumps, have been a part of BSD since its beginnings in Research UNIX. A core dump is a copy of memory that is saved on secondary storage by the kernel for debugging a system failure1. Though 38 years have passed since doadump() came about in UNIX/32V, core dumps are still needed and utilized in much the same way they were then. Given this, one might assume the core dump code changed little over time but, with some research, this assumption has proven incorrect. What has changed over time is where core dumps are sent to and what processor architectures are supported. Previous to the advent of UNIX, core dumps were printed to a line printer or punch cards. At the birth of UNIX core dumps were made to magnetic tape and because UNIX only supported the PDP-11, it was the only architecture supported for dumps. Over time machine architecture support has evolved from different PDP-11 models to hp300, i386 up to the present day with AMD64 and ARM64. In addition the type of dump device has changed from tape, to hard disk or another machine over a LAN. The following paper begins with a quick background on what core dumps are and why operators might need them. Following that the current state of the core dump facility and some of the more common extensions in use are examined. We conclude with a call to action for upstreaming these extensions and modularizing the core dump code such that different methods of core dump can be dynamically loaded into the kernel on demand. In addition a complete history of core dumps in UNIX and BSD was produced as research for this paper and can be found in the appendix.]]>
Crash dumps, also known as core dumps, have been a part of BSD since its beginnings in Research UNIX. A core dump is a copy of memory that is saved on secondary storage by the kernel for debugging a system failure1. Though 38 years have passed since doadump() came about in UNIX/32V, core dumps are still needed and utilized in much the same way they were then. Given this, one might assume the core dump code changed little over time but, with some research, this assumption has proven incorrect. What has changed over time is where core dumps are sent to and what processor architectures are supported. Previous to the advent of UNIX, core dumps were printed to a line printer or punch cards. At the birth of UNIX core dumps were made to magnetic tape and because UNIX only supported the PDP-11, it was the only architecture supported for dumps. Over time machine architecture support has evolved from different PDP-11 models to hp300, i386 up to the present day with AMD64 and ARM64. In addition the type of dump device has changed from tape, to hard disk or another machine over a LAN. The following paper begins with a quick background on what core dumps are and why operators might need them. Following that the current state of the core dump facility and some of the more common extensions in use are examined. We conclude with a call to action for upstreaming these extensions and modularizing the core dump code such that different methods of core dump can be dynamically loaded into the kernel on demand. In addition a complete history of core dumps in UNIX and BSD was produced as research for this paper and can be found in the appendix.]]> Sat, 25 Mar 2017 15:21:55 GMT /slideshow/the-history-and-future-of-core-dumps-in-freebsd/73634626 samgwydir@slideshare.net(samgwydir) The History and Future of Core Dumps in FreeBSD samgwydir Crash dumps, also known as core dumps, have been a part of BSD since its beginnings in Research UNIX. A core dump is a copy of memory that is saved on secondary storage by the kernel for debugging a system failure1. Though 38 years have passed since doadump() came about in UNIX/32V, core dumps are still needed and utilized in much the same way they were then. Given this, one might assume the core dump code changed little over time but, with some research, this assumption has proven incorrect. What has changed over time is where core dumps are sent to and what processor architectures are supported. Previous to the advent of UNIX, core dumps were printed to a line printer or punch cards. At the birth of UNIX core dumps were made to magnetic tape and because UNIX only supported the PDP-11, it was the only architecture supported for dumps. Over time machine architecture support has evolved from different PDP-11 models to hp300, i386 up to the present day with AMD64 and ARM64. In addition the type of dump device has changed from tape, to hard disk or another machine over a LAN. The following paper begins with a quick background on what core dumps are and why operators might need them. Following that the current state of the core dump facility and some of the more common extensions in use are examined. We conclude with a call to action for upstreaming these extensions and modularizing the core dump code such that different methods of core dump can be dynamically loaded into the kernel on demand. In addition a complete history of core dumps in UNIX and BSD was produced as research for this paper and can be found in the appendix. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/freebsd-coredump-history-slides-170325152155-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Crash dumps, also known as core dumps, have been a part of BSD since its beginnings in Research UNIX. A core dump is a copy of memory that is saved on secondary storage by the kernel for debugging a system failure1. Though 38 years have passed since doadump() came about in UNIX/32V, core dumps are still needed and utilized in much the same way they were then. Given this, one might assume the core dump code changed little over time but, with some research, this assumption has proven incorrect. What has changed over time is where core dumps are sent to and what processor architectures are supported. Previous to the advent of UNIX, core dumps were printed to a line printer or punch cards. At the birth of UNIX core dumps were made to magnetic tape and because UNIX only supported the PDP-11, it was the only architecture supported for dumps. Over time machine architecture support has evolved from different PDP-11 models to hp300, i386 up to the present day with AMD64 and ARM64. In addition the type of dump device has changed from tape, to hard disk or another machine over a LAN. The following paper begins with a quick background on what core dumps are and why operators might need them. Following that the current state of the core dump facility and some of the more common extensions in use are examined. We conclude with a call to action for upstreaming these extensions and modularizing the core dump code such that different methods of core dump can be dynamically loaded into the kernel on demand. In addition a complete history of core dumps in UNIX and BSD was produced as research for this paper and can be found in the appendix.
The History and Future of Core Dumps in FreeBSD from Sam Gwydir
]]> 296 4 https://cdn.slidesharecdn.com/ss_thumbnails/freebsd-coredump-history-slides-170325152155-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://public.slidesharecdn.com/v2/images/profile-picture.png