problem with socket and task

[mojtaba nadi]

hello
We have written an application which creates 3 tasks. in the first task
(task_task1()) we want to receive some data using a UDP socket. using the
file 1.c the socket will be created and bind successfully. But after adding
recvfrom() (file 2.c line 79) rtems will crash. The output error messages
are in error.txt. We are using rtems-libbsd package and the tasks without
the socket in the first one ran without any error. I wonder if any body
could help us to solve this problem.

regards,
Mojtaba
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20190813/b24b181e/attachment.html>
-------------- next part --------------
*** taskes + queues TEST ***
nexus0: <RTEMS Nexus device>
cgem0: <Cadence CGEM Gigabit Ethernet Interface> on nexus0
miibus0: <MII bus> on cgem0
e1000phy0: <Marvell 88E1512 Gigabit PHY> PHY 0 on miibus0
e1000phy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX,                                                                                                                                                                              1000baseT-FDX-master, auto
cgem0: no mac address found, assigning random: 0e:b0:ba:5e:ba:11
info: cgem0: Ethernet address: 0e:b0:ba:5e:ba:11
zy7_slcr0: <Zynq-7000 slcr block> on nexus0
info: lo0: link state changed to UP
info: cgem0: link state changed to DOWN
add host 172.21.53.19: gateway cgem0
add net default: gateway 172.21.53.19
info: cgem0: link state changed to UP
He
*** FATAL ***
fatal source: 9 (RTEMS_FATAL_SOURCE_EXCEPTION)

R0   = 0x002d2940 R8  = 0x0000000b
R1   = 0x002d4080 R9  = 0x002d2940
R2   = 0x00215038 R10 = 0x002d4070
R3   = 0x002d4070 R11 = 0x00000000
R4   = 0x00000010 R12 = 0x002d4014
R5   = 0x00000000 SP  = 0x002d4010
R6   = 0x00000020 LR  = 0x00116a45
R7   = 0x002d4080 PC  = 0x00116a5a
CPSR = 0x200f0173 VEC = 0x00000004
FPEXC = 0x40000000
FPSCR = 0x00000000
D00 = 0x0000000000000000
D01 = 0x0a0a0a0a0a0a0a0a
D02 = 0x1012000010120000
D03 = 0x0000000000000000
D04 = 0x0010000000100002
D05 = 0x0000001000000000
D06 = 0x8040201008040201
D07 = 0x8040201008040201
D08 = 0x0000000000000000
D09 = 0x0000000000000000
D10 = 0x0000000000000000
D11 = 0x0000000000000000
D12 = 0x0000000000000000
D13 = 0x0000000000000000
D14 = 0x0000000000000000
D15 = 0x0000000000000000
D16 = 0x0000000000000000
D17 = 0x0000000000000024
D18 = 0x7ffffffeffffffff
D19 = 0xed4000a244c40c4c
D20 = 0x1d1f8828f6968353
D21 = 0x8b844000b3790621
D22 = 0x1b04f64213865842
D23 = 0x6236908242634001
D24 = 0x0024250de6893403
D25 = 0x3cf40d2c7e4c0805
D26 = 0xc002402220ff0500
D27 = 0x59fad871ed10278e
D28 = 0x0920925fd503240c
D29 = 0x41041490170a42ad
D30 = 0x00b4037407141002
D31 = 0x277ce208009040ba
RTEMS version: 5.0.0.8c66acc8dcb4d459c1f61f2d5f62a23d14e3af46
RTEMS tools: 7.4.1 20190514 (RTEMS 5, RSB be90fb89678206e469f2f9189eb290cec49fd8                                                                                                                                                                             27, Newlib 5c2a3661c)
executing thread ID: 0x08a01000c
executing thread name: TAS1


-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.c
Type: text/x-csrc
Size: 4918 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20190813/b24b181e/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.c
Type: text/x-csrc
Size: 4891 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20190813/b24b181e/attachment-0001.bin>