public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Mills <johnmills@speakeasy.net>
To: eCos Users <ecos-discuss@ecos.sourceware.org>
Cc: Gary Thomas <gary@mlbassoc.com>
Subject: Re: [ECOS] Memory leakage problem with GoAhead web server
Date: Wed, 06 Jun 2007 19:03:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0706061021520.28011-100000@otter.localdomain> (raw)
In-Reply-To: <4666C78E.1050700@mlbassoc.com>

Gary, eCos users -

Thanks. A search of eCos archives did turn up a lot of references - most
centering on GoAhead's 'socketSelect'. There was also one (c/o Grant
Edwards) regarding secure links and authorization which might be exactly
my problem, but I didn't find any detail on it. Does anyone have a
specific pointer to that issue?

Thanks.
 - John Mills

On Wed, 6 Jun 2007, Gary Thomas wrote:

> John Mills wrote:

> > I'm working on an embedded eCos/MIPS32/OpenSSL product which I recently 
> > converted from eCos' basic 'httpd' to the free version of the 'GoAhead' 
> > server. Now I experience memory leakage.

> Check the archives - this problem has been reported many times.
> I don't recall if a [proper] solution was ever found.


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-06-06 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 16:07 John Mills
2007-06-06 16:24 ` Gary Thomas
2007-06-06 19:03   ` John Mills [this message]
2007-06-07  3:16     ` Andrew Lunn
2007-06-07  4:08       ` John Mills
2007-06-07  4:43         ` [ECOS] " Grant Edwards
2007-06-07  8:49           ` Grant Edwards

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=Pine.LNX.4.44.0706061021520.28011-100000@otter.localdomain \
    --to=johnmills@speakeasy.net \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.com \
    --cc=john.m.mills@alum.mit.edu \
    /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).