Crash in RTEMS when doing TCP communication.

Sebastian Huber sebastian.huber at embedded-brains.de
Fri Nov 11 07:55:26 UTC 2016


An off hand guess is that you use an already closed file descriptor and thus access freed memory and destroyed data structures.

----- Ben Dart <Ben.Dart at adept.com> schrieb:
> I have a program for RTEMS 4.9.2. This works for most applications but we are having some issues right now. We are sending TCP packets to the system running RTEMS, if the tcp port is open and receiving and we are replying etc, everything works fine. But if we stop the tcp receiver, eventually we get a crash in RTEMS. We have had the following few stack dumps:
> 
> CRASH 1
> 0x3A010000 : bsp_ram_size
> 0x0032DED4 : soisconnected
> 0x0035D0F0 : tcp_input
> 0x0031914C : ip_input
> 0x00319C80 : ipintr
> 0x00323124 : rtems_bsdnet_event_receive
> 0x00323298 : soconnsleep
> 0x0036E980 : _Thread_Handler
> 0x0036E904 : _Objects_API_maximum_class
[...]

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber at embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.


More information about the users mailing list