From owner-freebsd-current@freebsd.org Sun Oct 23 19:24:13 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 184D0C1EAFF for ; Sun, 23 Oct 2016 19:24:13 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BEAF2363 for ; Sun, 23 Oct 2016 19:24:12 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190d-b57ff700000036e5-44-580d0d26d536 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by (Symantec Messaging Gateway) with SMTP id 88.E6.14053.62D0D085; Sun, 23 Oct 2016 15:19:03 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id u9NJJ1wS024376; Sun, 23 Oct 2016 15:19:01 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u9NJIw40010069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 23 Oct 2016 15:19:00 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id u9NJIvOs003612; Sun, 23 Oct 2016 15:18:57 -0400 (EDT) Date: Sun, 23 Oct 2016 15:18:57 -0400 (EDT) From: Benjamin Kaduk To: "O. Hartmann" cc: freebsd-current Subject: Re: was: CURRENT [r307305]: r307823 still crashing In-Reply-To: <20161023182436.4d3bac4f.ohartman@zedat.fu-berlin.de> Message-ID: References: <20161014104833.7a2ac588@freyja.zeit4.iv.bundesimmobilien.de> <20161015102242.3c0f2fbb.ohartman@zedat.fu-berlin.de> <20161015121321.25007de8.ohartman@zedat.fu-berlin.de> <20161023182436.4d3bac4f.ohartman@zedat.fu-berlin.de> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixG6nrqvOyxth8G8Cr8WcNx+YLP7O+sPk wOQx49N8Fo9T2w8yBjBFcdmkpOZklqUW6dslcGXsWvOUrWA1e8XnZQtZGhhvsXYxcnBICJhI 7FlZ3cXIxSEk0MYksXpKIwuEs5FRYmvvMSjnEJPEkUWf2CCcBkaJngVNTF2MnBwsAtoSJ77M Zgax2QRUJGa+2cgGYosI6EucazoNZjMLGEq8XHePHWSdsICNxIG7liBhTgEnieeTtoCN4RVw kFh98zzU/NeMEr1bvoLNFBXQkVi9fwoLRJGgxMmZT1ggZmpJLJ++jWUCo8AsJKlZSFILGJlW Mcqm5Fbp5iZm5hSnJusWJyfm5aUW6Rrp5WaW6KWmlG5iBIUkpyTvDsZ/d70OMQpwMCrx8J64 xBMhxJpYVlyZe4hRkoNJSZT3qCx3hBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR3hOcvBFCvCmJ lVWpRfkwKWkOFiVx3v9uX8OFBNITS1KzU1MLUotgsjIcHEoSvG48QI2CRanpqRVpmTklCGkm Dk6Q4TxAw19wgwwvLkjMLc5Mh8ifYtTlWPDj9lomIZa8/LxUKXHeKyBFAiBFGaV5cHPAqWQ3 k+orRnGgt4R5f4FU8QDTENykV0BLmICWCMbzgCwpSURISTUwxtT8eZobV1J5+mmij3Bw1cZv GavSZoVv/LPv1Rxe4aKjYZ+2FxderQjJnDyvPl36wr57HE2X30//rfTmkdGviAqDGQdm1mz5 ++7hGnG9LtZDcz2FpbVP717h1vTlSV6zwsVFBiefPLMrO50wQzCq2dCg5d6VSaXej/h5uvRq QjX2pUnkd/8RU2Ipzkg01GIuKk4EAA3/f74AAwAA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2016 19:24:13 -0000 On Sun, 23 Oct 2016, O. Hartmann wrote: > How can I track a memory leak? I think I did not read enough of the context, but vmstat and top can track memory usage as a general thing. > How can I write to disk the backtrace given by the debugger when > crashing? My box I can freely test is using the nVidia BLOB and vt(), so > I can not see the backtrace. I got a very bad screenshot on one of my > laptops, but its so ugly/unreadable, I think it is unsuable to be > presented within this list at a reasonable size (200 kB max ist too > small). The backtrace should be part of the crash dump that is written to the (directly connected, non-encrypted, non-USB) swap device. "call doadump" at the debugger prompt (even typing blind) is supposed to make sure there's a dump taken. With respect to the screenshot, you should be able to post the image on an external site and send a link to the list, at least. -Ben