public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Colin Ford <colin.ford@pipinghotnetworks.com>
To: Ecos Mailing List <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Memory Problems Under eCos
Date: Thu, 30 Nov 2000 08:06:00 -0000	[thread overview]
Message-ID: <3A267AE0.8F4B2FB1@pipinghotnetworks.com> (raw)

Hello,

I'm still finding that my GoAhead web server runs out of
memory. I've traced it a bit further and found that when
a request comes through memory is trying to be freed but
the bp->flags have been corrupted and the integrity
not valid anymore.

It seems that the following gets corrupted:

  ../sockGen.c:712
  ../webs.c:2108
  ../sockGen.c:716
  ../sockGen.c:714

These then mount up by one each time and eventually
I run out of memory.......Doh!

So I reckon that its eCos. Ho well I'll carry on looking.

Thanks,
Col.

--
===========================================
Colin Ford               PipingHot Networks
Software Engineer        +44 (0)1364 655510



             reply	other threads:[~2000-11-30  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30  8:06 Colin Ford [this message]
2000-11-30  9:00 ` Hugo Tyson
2000-11-30  9:42   ` 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=3A267AE0.8F4B2FB1@pipinghotnetworks.com \
    --to=colin.ford@pipinghotnetworks.com \
    --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).