From: Hugo Tyson <hmt@redhat.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Memory Problems Under eCos
Date: Thu, 30 Nov 2000 09:00:00 -0000 [thread overview]
Message-ID: <wwtpujdtnah.fsf@masala.cygnus> (raw)
In-Reply-To: <3A267AE0.8F4B2FB1@pipinghotnetworks.com>
Colin Ford <colin.ford@pipinghotnetworks.com> writes:
> 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.
I know 0.0 about the context here, but when I'm debugging and I see stuff
like that, what I do is severalfold:
a) run with asserts enabled if you're not already
b) make your stacks much bigger - eCos does NOT do stack checking
c) make your malloc heap much bigger (if that applies to your platform) -
a failed malloc returns NULL, which can go undetected.
[Sorry if this is preaching to the converted...]
What's a bp-> ? Is it an eCos data structure or part of GoAhead?
Those source files are references to allocation calls or pointers?
(If anyone else has more context here and can help properly, ignore me)
- Huge
next prev parent reply other threads:[~2000-11-30 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 8:06 Colin Ford
2000-11-30 9:00 ` Hugo Tyson [this message]
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=wwtpujdtnah.fsf@masala.cygnus \
--to=hmt@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.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).