Date: Mon, 19 Nov 2018 15:16:12 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 227720] Kernel panic in ppp server Message-ID: <bug-227720-7501-A5v8TroBrY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227720-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-227720-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227720 --- Comment #38 from Franck Rousseau <Franck.Rousseau@imag.fr> --- Hi all, some additional information on this crash. The procedure that I describe in the previous post crashes consistently, wh= ich is a good point to start debugging. I suspect the crash to come from intern= al structures that are left corrupted at some point, after which there are sev= eral symptoms, like cannot intuit interface, no memory allocated, and ultimately= a kernel crash. I have compiled a new kernel with DDB support enabled, hopping to be able to inspect memory at runtime, but the address of the (struct rtentry *) is different each time. Does anyone has an idea on how can I get the address t= hat I need to watch to track who is modifying the routing table? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227720-7501-A5v8TroBrY>