Hi,

I thought I would bring you all up to date with
shttpd and RTEMS.

RTEMS now includes simple httpd in its distribution.
It looks functional to me although all I have done
is serve a static page with text and an embedded
graphic.


Issue #1: In building for the avr and h8300, there 
were errors.  When I investigated, I came across
this in shttpd:

defs.h:#define  URI_MAX         32768           /* Maximum URI 
size            */
log.c:  char    date[64], buf[URI_MAX];
log.c:  char    date[64], buf[URI_MAX], *q1 = "\"", *q2 = "\"";
shttpd.c:       char            path[URI_MAX], buf[1024];

These put 32K on the stack.  This is extremely excessive
for most embedded applications (4-8K fixed stacks are 
typical) and over the memory limits for stacks on the 
CPUs that flagged this.  Is there anything
that can be done about these?

Issue #2: GCC dies with an internal compiler error
on the long snprintf() calls in log.c on the Coldfire.
Ralf discovered that splitting the snprintf call
into multiple ones works around the problem.  So this has
a workaround in our tree if you want it.

Issue #3: General cleanup.  Ralf has ifdef'ed out most if not
all of the use of my_XXX for rtems.  He also made all non-public
symbols start with _shttp_ to avoid conflicts in statically
linked embedded applications.  He added support for using 
native MD5 routines since we already had these.  And there
was some C99 type cleanup.

Issue #1 is outstanding and I would like to see it 
addressed, although I have no idea what the right thing
to do is.  The others are included in the RTEMS 
CVS version of shttpd.

I would like to keep us close to your source so if you are 
interested, you can peruse the RTEMS CVS for the changes.

--joel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
shttpd-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shttpd-general

Reply via email to