On Tue, Jul 09, 2002 at 10:37:20AM -0700, Matthew Dillon wrote:
> Welcome to -current. I haven't been able to get crash dumps to
> work for a while :-(
>
> I usually set up a serial console between two machines and run
> gdb live to debug the kernel.
Crash dumps have been worki
:
:OK. How the * do I get a *!@#$@$#% crash dump on current? I
:did a dumpon to enable the dumping, which appeared to work. I then
:did a savecore after the system came back up (but before any swapping
:happened) and that seemed to work. I then tried to use gdb to read
:the core dump and
On 09-Jul-2002 M. Warner Losh wrote:
> OK. How the * do I get a *!@#$@$#% crash dump on current? I
> did a dumpon to enable the dumping, which appeared to work. I then
> did a savecore after the system came back up (but before any swapping
> happened) and that seemed to work. I then tried
On Tue, Jul 09, 2002 at 11:20:52AM -0500, Dan Nelson wrote:
> In the last episode (Jul 09), M. Warner Losh said:
> > OK. How the * do I get a *!@#$@$#% crash dump on current? I
> > did a dumpon to enable the dumping, which appeared to work. I then
> > did a savecore after the system came ba
In the last episode (Jul 09), M. Warner Losh said:
> OK. How the * do I get a *!@#$@$#% crash dump on current? I
> did a dumpon to enable the dumping, which appeared to work. I then
> did a savecore after the system came back up (but before any swapping
> happened) and that seemed to work.
OK. How the * do I get a *!@#$@$#% crash dump on current? I
did a dumpon to enable the dumping, which appeared to work. I then
did a savecore after the system came back up (but before any swapping
happened) and that seemed to work. I then tried to use gdb to read
the core dump and got the
