Date: Tue, 12 Feb 2019 13:53:38 -0500 From: Mark Johnston <markj@freebsd.org> To: Eugene Grosbein <eugen@grosbein.net> Cc: FreeBSD stable <freebsd-stable@freebsd.org> Subject: Re: 11.2-STABLE kernel wired memory leak Message-ID: <20190212185337.GD29847@raichu> In-Reply-To: <a107e663-9ac1-0169-0709-7028733118a3@grosbein.net> References: <d8c7abc0-3ba1-40e4-22b1-1b30d28ced14@grosbein.net> <20190212163446.GA29847@raichu> <4ab1331f-80e3-b856-b402-9985e73618bc@grosbein.net> <20190212181805.GB29847@raichu> <973d9dc6-8dd4-8cdf-b279-f5c9483da884@grosbein.net> <20190212184256.GC29847@raichu> <a107e663-9ac1-0169-0709-7028733118a3@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 13, 2019 at 01:48:21AM +0700, Eugene Grosbein wrote: > 13.02.2019 1:42, Mark Johnston wrote: > > >> Yes, I have debugger compiled into running kernel and have console access. > >> What commands should I use? > > > > I meant kgdb(1). If you can run that, try: > > > > (kgdb) p time_uptime > > (kgdb) p lowmem_uptime > > > > If you are willing to drop the system into DDB, do so and run > > > > db> x time_uptime > > db> x lowmem_uptime > > I will reach the console next day only. Is it wise to use kgdb over ssh for running remote system? :-) It should be fine. kgdb opens /dev/(k)mem read-only.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190212185337.GD29847>