Date: Sun, 23 Oct 2016 15:18:57 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: was: CURRENT [r307305]: r307823 still crashing Message-ID: <alpine.GSO.1.10.1610231515170.5272@multics.mit.edu> In-Reply-To: <20161023182436.4d3bac4f.ohartman@zedat.fu-berlin.de> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1610231515170.5272>