Date: Mon, 2 Sep 2002 19:57:17 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Marc G. Fournier" <scrappy@hub.org> Cc: <freebsd-stable@FreeBSD.ORG> Subject: Re: Crash with KVM monitoring in place ... Message-ID: <15731.64221.946462.504908@grasshopper.cs.duke.edu> In-Reply-To: <20020902203017.H2186-100000@hub.org> References: <15731.55567.174393.782218@grasshopper.cs.duke.edu> <20020902203017.H2186-100000@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Marc G. Fournier writes:
> Okay, do I have to do anything special on the dump_server side of things?
> Do you know of any way of inducing a 'panic' on a remote server to test
> this with? Would hate to set it all up and find out it doesn't work :)
To induce a panic, I built /usr/share/examples/kld/dyn_sysctl
with an intentional null-pointer deref bug in
sysctl_dyn_sysctl_test():
printf("intentional panic %d\n", *(int *)0);
Load it, then do "sysctl -a" -- kaboom.
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15731.64221.946462.504908>