This is the mail archive of the ecos-discuss@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Trouble using lwIP (driver crash...)


I found what cause limits.h to include cyg/fileio/limits.h.

In eCos Configuration Tool, under ISO C and POSIX infrastructure, there is a
Limits section. In this section, there are OPEN_MAX and NAME_MAX
implementation header that points to <cyg/fileio/limits.h>. Both were
checked.
I don't know why there were checked, since by default they are not. I
unchecked them and now the build works.


For the nc_test_slave, I will only test with the UDP part, so SO_REUSE will
not be a problem. I put this in comments, compile and run. When I ping it, I
got:

Stack base corrupt - i: 0
...
...
ASSERT FAIL: <A>thread.inl[119]void Cyg_HardwareThread::check_stack() Stack
base corrupt

Any idea what causes this?


Thanks,
Michael

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch] 
Sent: April 4, 2006 9:34 AM
To: Michael Grimard
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Trouble using lwIP (driver crash...)

On Tue, Apr 04, 2006 at 09:20:28AM -0400, Michael Grimard wrote:
> Hi,
> 
> When I compile without the File IO package I got:
> 
> In file included from
> /my_path_to_ecos/ecos/packages/infra/current/src/diag.cxx:65:
> /my_path_to_ecos/ecos_lwip_install/include/limits.h:175:37:
> cyg/fileio/limits.h: No such file or directory

This does not look like a direct lwip problem. 

Could you find out why limits.h is trying to include
cyg/fileio/limits.h. To me it seems like a configuration problem, but
i'm jumping to a conclusion with very limmited information. Could you
export your configuration and post it.

> For nc_test_slave, I got the "Not Applicable" message when I ran it, but I
> didn't try it before running nc_test_master, since nc_test_slave is part
of
> the tests that come with lwIP. Maybe, it needs to be remove?

The reason the test has been kept is that we hope the upstream
maintains of lwip will put back the setsockopt() calls the test needs.

        Andrew


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]