Propose for Several Dump types

Jun Su csujun at gmail.com
Wed Dec 15 00:36:54 PST 2004


On Wed, 15 Dec 2004 08:51:21 +0100, Poul-Henning Kamp
<phk at phk.freebsd.dk> wrote:
> In message <cd4370cf04121417446c96319f at mail.gmail.com>, Jun Su writes:
> >On Tue, 14 Dec 2004 08:48:44 +0100, Poul-Henning Kamp
> ><phk at phk.freebsd.dk> wrote:
> >> In message <cd4370cf04121323433255da9d at mail.gmail.com>, Jun Su writes:
> >>
> >> >MiniDump
> >> >=======
> >> >In a minidump, Register info, plus the crash stack is enough.
> >>
> >> Make it an EVENTHANDLER() and dump it in ascii format.
> >                                                       ^^^^^^^^^^^^
> >Don't think the ascii format is a good choose. We can only dump the
> >information like the ones we can get in the KDB. My propose is storing
> >the pages that the stack point is in. Then we can get more useful
> >stack in the userland with the kernel file and kernel symbol.
> 
> An ascii format summary is a _great_ format because people can email
> us it without knowing anything else.  We could in fact make it
> a /etc/rc.conf tunable:  "send_panic_reports=YES" and we would
> receive it in email whenever a crash occured.
We can also create an automation system to collect these information.
When the number of crash in same function reaches a thorehold, it will
send a report to a ML. :-) Sounds your idea is interesing.
Anyway, I still think ascii format dump can not replace the minidump.
Minidump can provide more information.
> 
> --
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk at FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetence.
> 


-- 
-- Jun Su


More information about the freebsd-arch mailing list