Comments on: Saving crash dumps https://www.dragonflydigest.com/2004/05/23/saving-crash-dumps/ A running description of activity related to DragonFly BSD. Mon, 24 May 2004 01:04:33 +0000 hourly 1 https://wordpress.org/?v=7.0.4 By: Lazarus https://www.dragonflydigest.com/2004/05/23/saving-crash-dumps/comment-page-1/#comment-253 Mon, 24 May 2004 01:04:33 +0000 http://www.shiningsilence.com/dbsdlog/?p=402#comment-253 Fair enough.

Just curious, but couldn’t there be a default option for a kernel only crash dump, like in Windows XP, and an optional full memory crash dump?

Seems like a reasonable compromise from my POV…

]]> By: Emiel Kollof https://www.dragonflydigest.com/2004/05/23/saving-crash-dumps/comment-page-1/#comment-252 Mon, 24 May 2004 00:59:12 +0000 http://www.shiningsilence.com/dbsdlog/?p=402#comment-252 well, vmcore files tend to eat up a lot of space. If you have e.g. 512 MB of mem, your vmcore will be 512 MB big. Also, not everyone has dfbsd installed on ad0s1 (like me). It makes more sense to enable the var in rc.conf by hand than to enable it as a default.

You are right that there could be a little blurb about it in the installation README.

]]> By: Lazarus https://www.dragonflydigest.com/2004/05/23/saving-crash-dumps/comment-page-1/#comment-251 Sun, 23 May 2004 14:32:58 +0000 http://www.shiningsilence.com/dbsdlog/?p=402#comment-251 I’ve always wondered why these settings were not default in development versions of OSs like DragonFly.

Sure knowledgable users know how to do this, but if all you needed to do was ask a new user to send a copy of a crash dump file that was automatically generated and saved, it might save the developers some headaches while trying to track down issues discovered by less technical folks.

]]>