RTEMS 4.9.5 vs 4.10.2 Network Stack
Pierre Ficheux
pierre.ficheux at openwide.fr
Tue Aug 28 15:57:21 UTC 2012
Le 27/08/2012 23:32, SAeeD a écrit :
> As I traced the execution of RTEMS 4.10.2 with a simple TCP client
> application on QEMU, I got this experimental:
> After setting up a TCP server in PC, I executed the TCP client on
> Mini2440 and traced the execution. A socket is created with socket
> descriptor #3. Every thing seems fine but when calling function
> "connect", after a long time hanging on the line 161 of the following
> context (rtems_syscall.c where function "connect" if implemented.), an
> error numbered #116 happens and I got out of the loop and return -1 as
> the return value of function "connect". This is the context:
>
> 160 while ((so->so_state & SS_ISCONNECTING) && so->so_error == 0) {
> 161 error = soconnsleep (so);
> 162 if (error)
> 163 break;
> 164 }
> 165 if (error == 0) {
> 166 error = so->so_error;
> 167 so->so_error = 0;
> 168 }
> 169 bad:
> 170 so->so_state &= ~SS_ISCONNECTING;
> 171 m_freem (nam);
> 172 if (error)
> 173 errno = error;
> 174 else
> 175 ret = 0;
> 176 rtems_bsdnet_semaphore_release ();
> 177 return ret;
>
> What could be the possible problem? What is the meaning of error #116?
I think error is ETIMEDOUT, I got the same error 116 when trying tu use
BOOTP (in bootpc_call() function).
--
Pierre FICHEUX -/- CTO OWI, France -\- pierre.ficheux at openwide.fr
http://ingenierie.openwide.fr
http://www.ficheux.org
I would love to change the world, but they won't give me the source code
More information about the users
mailing list