Date: Fri, 11 Jan 2013 07:46:05 +0200 From: Vadim Urazaev <demiurg@tica.com.ua> To: =?ISO-8859-2?Q?Radek_Krej=E8a?= <radek.krejca@starnet.cz> Cc: freebsd-ipfw@freebsd.org, freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: RE: kern/174749: Unexpected change of default route Message-ID: <CAAEEwq3gKpFr8FaeaeUWC%2BM=dLcPa1YsqwfuSJF9pbw0Z6z4Ng@mail.gmail.com> In-Reply-To: <B2E0472020754D45B72E9B0CE35278CA94F0C8A4CF@EXCHANGE.mail.starnet.cz> References: <201301101140.r0ABe1J0004000@freefall.freebsd.org> <CAAEEwq37J%2BepywJMZP_mRkkyN1XKi3A_ZaLhbkARsYh0NRC=sg@mail.gmail.com> <B2E0472020754D45B72E9B0CE35278CA94F0C8A4CF@EXCHANGE.mail.starnet.cz>
index | next in thread | previous in thread | raw e-mail
Do some body know how can we debug kernel memory corruption on live system? We need to find out which function/subsystem is cause of this mess. Or maybe is there some way to lock particular memory area, where default gateway lies and watch which subsystem will cause system crash?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAAEEwq3gKpFr8FaeaeUWC%2BM=dLcPa1YsqwfuSJF9pbw0Z6z4Ng>