This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: thread heap leak?
- From: Andreas Schwab <schwab at suse dot de>
- To: David Muse <david dot muse at firstworks dot com>
- Cc: "Carlos O'Donell" <codonell at redhat dot com>, Florian Weimer <fw at deneb dot enyo dot de>, libc-alpha at sourceware dot org
- Date: Mon, 01 Apr 2019 10:19:53 +0200
- Subject: Re: thread heap leak?
- References: <20190322105304.1e848cefb45fb65d32a96b23@firstworks.com> <77992b67-3fdf-cad7-8ad8-0e27b9353791@redhat.com> <20190322133932.b5b9b2af28ec5941af810f21@firstworks.com> <6ff37227-4b52-25c5-d890-02b4becb2ae8@redhat.com> <20190325113758.73e9324a19727503d82d2d4c@firstworks.com> <20190330130635.c9e52acd94c8248c20709e92@firstworks.com> <c920f08b-85c6-6bd3-5ca4-7c9bebee3a99@redhat.com> <20190331231847.4e46776b2625e1d436607cbb@firstworks.com>
On Mär 31 2019, David Muse <david.muse@firstworks.com> wrote:
> Yeah, that is what it looks like, but where did the 3rd thread stack come from? As far as I can tell, no thread created it.
Try using `strace -k -e mmap' to see where the mapping is created.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."