Re: Propose for Several Dump types
From: Jun Su (csujun_at_gmail.com)
Date: 12/15/04
- Previous message: Kirk McKusick: "Re: Propose for Several Dump types"
- In reply to: Poul-Henning Kamp: "Re: Propose for Several Dump types"
- Next in thread: Poul-Henning Kamp: "Re: Propose for Several Dump types"
- Reply: Poul-Henning Kamp: "Re: Propose for Several Dump types"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 15 Dec 2004 16:36:53 +0800 To: Poul-Henning Kamp <phk@phk.freebsd.dk>
On Wed, 15 Dec 2004 08:51:21 +0100, Poul-Henning Kamp
<phk@phk.freebsd.dk> wrote:
> In message <cd4370cf04121417446c96319f@mail.gmail.com>, Jun Su writes:
> >On Tue, 14 Dec 2004 08:48:44 +0100, Poul-Henning Kamp
> ><phk@phk.freebsd.dk> wrote:
> >> In message <cd4370cf04121323433255da9d@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@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 _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Kirk McKusick: "Re: Propose for Several Dump types"
- In reply to: Poul-Henning Kamp: "Re: Propose for Several Dump types"
- Next in thread: Poul-Henning Kamp: "Re: Propose for Several Dump types"
- Reply: Poul-Henning Kamp: "Re: Propose for Several Dump types"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: Propose for Several Dump types
... >> Make it an EVENTHANDLERand dump it in ascii format. ... >stack
in the userland with the kernel file and kernel symbol. ... (freebsd-arch) - Re: Minidump
... Is it possible to create a dump at runtime from a normal user pc via code, ...
> Yes that gives stacktrace but i asked for a minidump, ... (microsoft.public.dotnet.languages.vb) - Re: BSOD- need help!
... Source: Save Dump ... but it'll keep your machine from rebooting. ...
Choosing recovery actions if Windows stops unexpectedly ... Memory "Dumps" and Memory.dmp
or Minidump File here... ... (microsoft.public.windowsxp.help_and_support) - Re: Propose for Several Dump types
... >>In a minidump, Register info, plus the crash stack is enough. ... >
Make it an EVENTHANDLERand dump it in ascii format. ... Don't think the ascii format
is a good choose. ... stack in the userland with the kernel file and kernel symbol. ...
(freebsd-arch) - Re: minidump
... Once a minidump is uploaded to Microsoft ... > my dump and upload
it. ... It has instructions on how to find the dump file. ... > The normal
aborts that get sent to MS - what happens to them? ... (microsoft.public.windowsxp.general)