RE: [ECOS] goAhead not going ahead...

RE: [ECOS] goAhead not going ahead...

[Doug Fraser]

Are you using their memory allocator?
Are you declaring each page complete? (I can't remember the call)
I have used goahead under vxWorks and was
very happy with it. It was easy to add persistent
push processing by spawning tasks on certain CGI pages.
Nice tool, especially given the price.

On another note....

Has anyone successfully built the GDB stubs under 1.3.1??
I get linker (address not in RAM) failures....

Doug

-----Original Message-----
From: Colin Ford [ mailto:colin.ford@pipinghotnetworks.com ]
Sent: Monday, October 30, 2000 11:22 AM
To: Ecos Mailing List
Subject: [ECOS] goAhead not going ahead...


Hello,

I sent a message earlier about goAhead stopping serving
pages after a while. Well it seems that its running out of
memory. Something not being freed?

Anyone got a fix?
Cheers,
Col.

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

RE: [ECOS] goAhead not going ahead...

[Robert Cragie]

It's a long shot, but it might be heap fragmentation problems. I have
certainly had problems in similar applications using heap allocation with
larg(ish) images. I fixed it using pool memory (i.e. using arrays of
different sized memory chunks). This is wasteful as it typically
overallocates, but there are no fragmentation problems.

Robert Cragie

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com
> [ mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Colin Ford
> Sent: 30 October 2000 16:22
> To: Ecos Mailing List
> Subject: [ECOS] goAhead not going ahead...
>
>
> Hello,
>
> I sent a message earlier about goAhead stopping serving
> pages after a while. Well it seems that its running out of
> memory. Something not being freed?
>
> Anyone got a fix?
> Cheers,
> Col.
>
> --
> ===========================================
> Colin Ford               PipingHot Networks
> Software Engineer        +44 (0)1364 655510
>
>
>

[ECOS] goAhead not going ahead...

[Colin Ford]

Hello,

I sent a message earlier about goAhead stopping serving
pages after a while. Well it seems that its running out of
memory. Something not being freed?

Anyone got a fix?
Cheers,
Col.

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

RE: [ECOS] GoAhead not going ahead....

[Gary Thomas]

On 30-Oct-2000 Colin Ford wrote:
> Hello All,
> 
> I've got the goAhead server running on my mips processor,
> which was quite easy. The only problem is that if I try to
> make it reload a page with a jpg on it more than about 15
> times the goAhead server seems to stop responding, my
> background task led blinking stops and nothing moves.
> 
> I'm using the latest CVS eCos and the latest goAhead.
> 
> Anyone else seen this?

I observed some similar problems, which I traced down to their
internal 'malloc()' functions.  I did not have time to fully
debug it though.

It's a place to start looking.

[ECOS] GoAhead not going ahead....

[Colin Ford]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Hello All,
I've got the goAhead server running on my mips processor,
which was quite easy. The only problem is that if I try to
make it reload a page with a jpg on it more than about 15
times the goAhead server seems to stop responding, my
background task led blinking stops and nothing moves.
I'm using the latest CVS eCos and the latest goAhead.
Anyone else seen this?
Many thanks,
Col.
 
-- 
===========================================
Colin Ford               PipingHot Networks
Software Engineer        +44 (0)1364 655510