From: "Kapania, Ashish" <akapania@ti.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Possible bug in __sfp() libc routine
Date: Fri, 07 Apr 2017 21:58:00 -0000 [thread overview]
Message-ID: <C0BBAD24E8CD0E4B8A8BD70B11D9544415CB3BBA@DFLE08.ent.ti.com> (raw)
Hi All,
In the __sfp() function in "libc/findfp.c" file, I see that if no free FILE object is found, one is allocated and put on a list in the global re-entrancy structure (_GLOBAL_REENT). This seems like a bug to me. I believe the FILE object should be put on a list in the thread specific reentrancy structure. If I create a thread, do a fopen, do a fwrite (invokes __sfp which in turn allocates the FILE object), do a fclose and then delete the thread, the FILE object allocated by __sfp() is not freed. If a do this sequence repeatedly, I see memory keeps leaking until my app runs out of heap. I have a separate re-entrancy structure for each thread but because the FILE object is not in a list on the local re-entrancy structure, it does not get freed when I delete the thread and run _reclaim_reent() on the local reentrancy structure.
Any thoughts ?
Best,
Ashish
next reply other threads:[~2017-04-07 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 21:58 Kapania, Ashish [this message]
2017-04-08 21:04 ` Freddie Chopin
2017-04-10 19:53 ` Kapania, Ashish
2017-04-11 11:52 ` AW: " onkel.jack
2017-04-09 9:22 ` Martin Velek
2018-01-19 0:31 ` Kapania, Ashish
2017-04-07 22:02 Kapania, Ashish
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=C0BBAD24E8CD0E4B8A8BD70B11D9544415CB3BBA@DFLE08.ent.ti.com \
--to=akapania@ti.com \
--cc=newlib@sourceware.org \
/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: link
Be 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).