From: John Paul King <jpking@advantexmail.net>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Termios memory leak?
Date: Sun, 17 Jul 2005 21:34:00 -0000 [thread overview]
Message-ID: <42DACD46.3090308@advantexmail.net> (raw)
I've been using eCos w/ termios serial ports, and it seems that each
open/close of such devices allocates memory that is never freed. Struct
termios_private_info has a member 'errbuf' that is malloc'd in function
'real_termios_init' (packages/io/serial/src/common/termiostty.c), but I
never see a corrseponding 'free'. I grep'd through the source, and I
haven't seen any actions taken on 'errbuf' (other than allocation within
termiostty), so is it even used in eCos? I have temporarily removed the
few lines that deal w/ 'errbuf', and my application seems to work
properly now, but is this a safe thing to do?
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-07-17 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 21:34 John Paul King [this message]
2005-07-18 16:37 Jay Foster
2005-07-21 18:02 ` Andrew Lunn
2005-07-26 17:25 ` Jonathan Larmour
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=42DACD46.3090308@advantexmail.net \
--to=jpking@advantexmail.net \
--cc=ecos-discuss@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: 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).