public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "apconole at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/5171] New: Memory leak in nptl pthread_create() call Date: Sat, 13 Oct 2007 01:13:00 -0000 [thread overview] Message-ID: <20071013011337.5171.apconole@yahoo.com> (raw) While testing out a heap management system, I noticed that there consistently appears to be 100 bytes or so leaked during the call to pthread_create. This memory is not reclaimed, even with explicit usage of pthread_exit. The PC of the leak, under gdb, yeilds the following: 0x4000dcc4 <allocate_dtv+52>: call 0x4000076c <completed.4497+939223960> 0x4000dcc9 <allocate_dtv+57>: test %eax,%eax The backtrace of this call: #0 0x4000dc9b in allocate_dtv () from /lib/ld-linux.so.2 #1 0x4000df3c in _dl_allocate_tls () from /lib/ld-linux.so.2 #2 0x441a78e5 in pthread_create@@GLIBC_2.1 () from /lib/tls/libpthread.so.0 #3 0x0804885a in main () at test.c:59 The reporting from valgrind confirms this: 272 bytes in 2 blocks are possibly lost in loss record 5 of 7 at 0x40046FF: calloc (vg_replace_malloc.c:279) by 0x446479E9: _dl_allocate_tls (in /lib/ld-2.5.so) by 0x447C79D6: pthread_create@@GLIBC_2.1 (in /lib/libpthread-2.5.so) by 0x80488BD: main (test.c:59) I can also dump the contents of these bytes, if needed. -- Summary: Memory leak in nptl pthread_create() call Product: glibc Version: 2.3.5 Status: NEW Severity: normal Priority: P2 Component: nptl AssignedTo: drepper at redhat dot com ReportedBy: apconole at yahoo dot com CC: glibc-bugs at sources dot redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5171 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2007-10-13 1:13 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-13 1:13 apconole at yahoo dot com [this message] 2007-10-15 4:04 ` [Bug nptl/5171] " drepper at redhat dot com 2009-01-29 16:05 ` vgabor at gmail dot com 2009-01-29 16:35 ` drepper at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20071013011337.5171.apconole@yahoo.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).