API tools faq
paste
dtorkin

Untitled

dtorkin
May 27th, 2025 (edited)
36
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.35 KB | None | 0 0
raw download clone embed print report
  1. dtorkin@ubuntu1:~/Desktop/practice$ sudo ./uvm_app --wait-for-gui OR
  2. UVM: Option --wait-for-gui enabled. Will wait for GUI connection.
  3. DEBUG UVM: Effective RadarMode selected: 0
  4. UVM: Загрузка конфигурации...
  5. Configuration parsed successfully from 'config.ini'.
  6. Found configurations for 4 SVM instances in file.
  7. --- Effective Configuration ---
  8. interface_type = ethernet
  9. UVM Target: 192.168.189.129:8080
  10. SVM 0: Port=8080, LAK=0x08 (Loaded: Yes)
  11. Simulate Control Failure: No
  12. Disconnect After: -1 messages
  13. Simulate Response Timeout: No
  14. Send Warning on Confirm: No (TKS: 1)
  15. SVM 1: Port=8081, LAK=0x09 (Loaded: Yes)
  16. Simulate Control Failure: No
  17. Disconnect After: -1 messages
  18. Simulate Response Timeout: No
  19. Send Warning on Confirm: No (TKS: 1)
  20. SVM 2: Port=8082, LAK=0x0A (Loaded: Yes)
  21. Simulate Control Failure: No
  22. Disconnect After: -1 messages
  23. Simulate Response Timeout: No
  24. Send Warning on Confirm: No (TKS: 1)
  25. SVM 3: Port=8083, LAK=0x0B (Loaded: Yes)
  26. Simulate Control Failure: No
  27. Disconnect After: -1 messages
  28. Simulate Response Timeout: No
  29. Send Warning on Confirm: No (TKS: 1)
  30. -----------------------------
  31. UVM: Found 4 SVM configurations in config file.
  32. Thread-safe UVM request queue created with capacity 50
  33. Thread-safe UVM Response queue created with capacity 200
  34. UVM: Connecting to SVMs...
  35. DEBUG UVM: IP before loop: 192.168.189.129
  36. UVM: Attempting to connect to SVM ID 0 (IP: 192.168.189.129, Port: 8080)...
  37. DEBUG UVM: Preparing to create interface for SVM 0 with IP=192.168.189.129, Port=8080
  38. Ethernet: Connected to 192.168.189.129:8080 (handle: 3)
  39. UVM: Successfully connected to SVM ID 0 (Handle: 3).
  40. UVM: Attempting to connect to SVM ID 1 (IP: 192.168.189.129, Port: 8081)...
  41. DEBUG UVM: Preparing to create interface for SVM 1 with IP=192.168.189.129, Port=8081
  42. Ethernet: Connected to 192.168.189.129:8081 (handle: 4)
  43. UVM: Successfully connected to SVM ID 1 (Handle: 4).
  44. UVM: Attempting to connect to SVM ID 2 (IP: 192.168.189.129, Port: 8082)...
  45. DEBUG UVM: Preparing to create interface for SVM 2 with IP=192.168.189.129, Port=8082
  46. Ethernet: Connected to 192.168.189.129:8082 (handle: 5)
  47. UVM: Successfully connected to SVM ID 2 (Handle: 5).
  48. UVM: Attempting to connect to SVM ID 3 (IP: 192.168.189.129, Port: 8083)...
  49. DEBUG UVM: Preparing to create interface for SVM 3 with IP=192.168.189.129, Port=8083
  50. Ethernet: Connected to 192.168.189.129:8083 (handle: 6)
  51. UVM: Successfully connected to SVM ID 3 (Handle: 6).
  52. UVM: Connected to 4 out of 4 configured SVMs.
  53. UVM: Запуск потоков Sender, Receiver(s) и GUI Server...
  54. UVM: Waiting for GUI client to connect on port 12345 (or press Ctrl+C)...
  55. UVM Receiver thread started for SVM ID 1 (handle: 4).
  56. UVM Sender thread started.
  57. UVM Receiver thread started for SVM ID 0 (handle: 3).
  58. UVM Receiver thread started for SVM ID 2 (handle: 5).
  59. GUI Server: Starting listener on port 12345
  60. UVM Receiver thread started for SVM ID 3 (handle: 6).
  61. GUI Server: Waiting for GUI connection on port 12345...
  62. receive_protocol_message: Соединение закрыто при чтении заголовка.
  63. Receiver Thread (SVM 1): Connection closed by SVM. Marking link as INACTIVE.
  64. UVM Receiver thread for SVM ID 1 finished.
  65. GUI Server: Accepted connection from 127.0.0.1:43480 (FD 8)
  66. GUI Server: Sending initial state to new GUI client (FD 8).
  67. GUI Server: Initial state sent to GUI client (FD 8).
  68. UVM: GUI client connected! Proceeding with SVM operations.
  69. UVM: All necessary threads started. Selected RadarMode: 0
  70. UVM: Начало основного цикла управления SVM (Асинхронная подготовка)...
  71. UVM Main (SVM 0): Отправка команды подготовки типа 128 (Num 0)...
  72. send_uvm_request: Вход. Запрос для SVM 0, тип протокольного сообщения 128, тип UVM запроса 1.
  73. UVM Main (SVM 0): Команда подготовки типа 128 (Num 0) отправлена. Переход в состояние ожидания 2.
  74. UVM Main (SVM 2): Отправка команды подготовки типа 128 (Num 0)...
  75. send_uvm_request: Вход. Запрос для SVM 2, тип протокольного сообщения 128, тип UVM запроса 1.
  76. UVM Main (SVM 2): Команда подготовки типа 128 (Num 0) отправлена. Переход в состояние ожидания 2.
  77. UVM Main (SVM 3): Отправка команды подготовки типа 128 (Num 0)...
  78. send_uvm_request: Вход. Запрос для SVM 3, тип протокольного сообщения 128, тип UVM запроса 1.
  79. UVM Main (SVM 3): Команда подготовки типа 128 (Num 0) отправлена. Переход в состояние ожидания 2.
  80. Отправка сообщения через Ethernet: Тип=128, Номер=0, Длина тела=2, Общий размер=8, Handle=3
  81. Отправка сообщения через Ethernet: Тип=128, Номер=0, Длина тела=2, Общий размер=8, Handle=5
  82. Отправка сообщения через Ethernet: Тип=128, Номер=0, Длина тела=2, Общий размер=8, Handle=6
  83. receive_protocol_message: Соединение закрыто при чтении заголовка.
  84. Receiver Thread (SVM 2): Connection closed by SVM. Marking link as INACTIVE.
  85. UVM Receiver thread for SVM ID 2 finished.
  86. receive_protocol_message: Соединение закрыто при чтении заголовка.
  87. Receiver Thread (SVM 0): Connection closed by SVM. Marking link as INACTIVE.
  88. UVM Receiver thread for SVM ID 0 finished.
  89. receive_protocol_message: Соединение закрыто при чтении заголовка.
  90. Receiver Thread (SVM 3): Connection closed by SVM. Marking link as INACTIVE.
  91. UVM Receiver thread for SVM ID 3 finished.
  92.  
  93.  
  94.  
  95. dtorkin@ubuntu1:~/Desktop/practice$ sudo ./svm_app
  96. SVM Multi-Port Server starting...
  97. SVM App-wide resources (srand) initialized.
  98. Message handlers initialized.
  99. SVM: Loading configuration...
  100. Configuration parsed successfully from 'config.ini'.
  101. Found configurations for 4 SVM instances in file.
  102. --- Effective Configuration ---
  103. interface_type = ethernet
  104. UVM Target: 192.168.189.129:8080
  105. SVM 0: Port=8080, LAK=0x08 (Loaded: Yes)
  106. Simulate Control Failure: No
  107. Disconnect After: -1 messages
  108. Simulate Response Timeout: No
  109. Send Warning on Confirm: No (TKS: 1)
  110. SVM 1: Port=8081, LAK=0x09 (Loaded: Yes)
  111. Simulate Control Failure: No
  112. Disconnect After: -1 messages
  113. Simulate Response Timeout: No
  114. Send Warning on Confirm: No (TKS: 1)
  115. SVM 2: Port=8082, LAK=0x0A (Loaded: Yes)
  116. Simulate Control Failure: No
  117. Disconnect After: -1 messages
  118. Simulate Response Timeout: No
  119. Send Warning on Confirm: No (TKS: 1)
  120. SVM 3: Port=8083, LAK=0x0B (Loaded: Yes)
  121. Simulate Control Failure: No
  122. Disconnect After: -1 messages
  123. Simulate Response Timeout: No
  124. Send Warning on Confirm: No (TKS: 1)
  125. -----------------------------
  126. SVM: Will attempt to start 4 instances based on config.
  127. DEBUG SVM MAIN - Instance 0 Settings: LAK=0x08, simulate_control_failure=0, disconnect_after=-1, simulate_timeout=0, send_warning=0, tks=1
  128. DEBUG SVM MAIN - Instance 1 Settings: LAK=0x09, simulate_control_failure=0, disconnect_after=-1, simulate_timeout=0, send_warning=0, tks=1
  129. DEBUG SVM MAIN - Instance 2 Settings: LAK=0x0A, simulate_control_failure=0, disconnect_after=-1, simulate_timeout=0, send_warning=0, tks=1
  130. DEBUG SVM MAIN - Instance 3 Settings: LAK=0x0B, simulate_control_failure=0, disconnect_after=-1, simulate_timeout=0, send_warning=0, tks=1
  131. Thread-safe QueuedMessage queue created with capacity 400
  132. SVM: Starting common Sender thread...
  133. SVM: Sender thread started. 4 listeners active. Running...
  134. SVM Main: Waiting for shutdown signal...
  135. Ethernet: Listening on port 8081 (handle: 3)
  136. Listener thread started for SVM ID 1 (LAK 0x09, Port 8081, Listen FD 3)
  137. Listener (SVM 1, Port 8081): Waiting for connection...
  138. SVM Sender thread started (reads global outgoing queue).
  139. Ethernet: Listening on port 8080 (handle: 5)
  140. Listener thread started for SVM ID 0 (LAK 0x08, Port 8080, Listen FD 5)
  141. Listener (SVM 0, Port 8080): Waiting for connection...
  142. Ethernet: Listening on port 8082 (handle: 7)
  143. Listener thread started for SVM ID 2 (LAK 0x0A, Port 8082, Listen FD 7)
  144. Listener (SVM 2, Port 8082): Waiting for connection...
  145. Ethernet: Listening on port 8083 (handle: 8)
  146. Listener thread started for SVM ID 3 (LAK 0x0B, Port 8083, Listen FD 8)
  147. Listener (SVM 3, Port 8083): Waiting for connection...
  148. Listener (SVM 0, Port 8080): Accepted connection from 192.168.189.128:52716 (Client FD 6)
  149. Thread-safe QueuedMessage queue created with capacity 100
  150. Listener (SVM 0, Port 8080): Instance activated. Worker threads (Recv, Proc, Timer) started.
  151. SVM Processor thread started for instance 0.
  152. InstanceTimer (ID 0, LAK 0x08): Thread started.
  153. InstanceTimer (ID 0, LAK 0x08): Thread finished.
  154. SVM Receiver thread started for instance 0 (LAK 0x08, handle: 6).
  155. Listener (SVM 1, Port 8081): Accepted connection from 192.168.189.128:37572 (Client FD 4)
  156. Thread-safe QueuedMessage queue created with capacity 100
  157. SVM Receiver thread started for instance 1 (LAK 0x09, handle: 4).
  158. Listener (SVM 2, Port 8082): Accepted connection from 192.168.189.128:58070 (Client FD 9)
  159. Thread-safe QueuedMessage queue created with capacity 100
  160. Listener (SVM 1, Port 8081): Instance activated. Worker threads (Recv, Proc, Timer) started.
  161. Listener (SVM 3, Port 8083): Accepted connection from 192.168.189.128:51446 (Client FD 10)
  162. Thread-safe QueuedMessage queue created with capacity 100
  163. Listener (SVM 3, Port 8083): Instance activated. Worker threads (Recv, Proc, Timer) started.
  164. SVM Receiver thread (Inst 1, LAK 0x09): Shutting down incoming queue and finishing.
  165. Thread-safe QueuedMessage queue shutdown initiated.
  166. SVM Receiver thread finished for instance 1 (LAK 0x09).
  167. InstanceTimer (ID 3, LAK 0x0B): Thread started.
  168. InstanceTimer (ID 3, LAK 0x0B): Thread finished.
  169. Listener (SVM 1, Port 8081): Receiver thread joined.
  170. SVM Processor thread started for instance 2.
  171. InstanceTimer (ID 2, LAK 0x0A): Thread started.
  172. InstanceTimer (ID 2, LAK 0x0A): Thread finished.
  173. Listener (SVM 2, Port 8082): Instance activated. Worker threads (Recv, Proc, Timer) started.
  174. SVM Processor thread started for instance 1.
  175. Processor Thread (Inst 1): Incoming queue empty and shutdown. Exiting.
  176. SVM Processor thread finished for instance 1.
  177. SVM Receiver thread started for instance 2 (LAK 0x0A, handle: 9).
  178. Listener (SVM 1, Port 8081): Processor thread joined.
  179. Listener (SVM 1, Port 8081): Signaled instance timer thread to stop.
  180. InstanceTimer (ID 1, LAK 0x09): Thread started.
  181. InstanceTimer (ID 1, LAK 0x09): Thread finished.
  182. Listener (SVM 1, Port 8081): Instance timer thread joined.
  183. Listener (SVM 1, Port 8081): Worker threads finished. Cleaning up instance...
  184. Ethernet: Closing handle 4
  185. SVM Receiver thread started for instance 3 (LAK 0x0B, handle: 10).
  186. Thread-safe QueuedMessage queue destroyed
  187. Listener (SVM 1, Port 8081): Instance deactivated. Ready for new connection.
  188. SVM Processor thread started for instance 3.
  189. Listener (SVM 1, Port 8081): Waiting for connection...
  190. DEBUG RECV: header_net.body_length (network order) = 0x0200 (512)
  191. DEBUG RECV: bodyLenHost (host order) = 2
  192. DEBUG RECV: message.header.body_length после message_to_host_byte_order (должен быть хост) = 2
  193. Получено сообщение через Ethernet: Тип=128, Номер=0, Длина тела=2, Handle=9
  194. DEBUG RECV: header_net.body_length (network order) = 0x0200 (512)
  195. DEBUG RECV: bodyLenHost (host order) = 2
  196. DEBUG RECV: message.header.body_length после message_to_host_byte_order (должен быть хост) = 2
  197. Получено сообщение через Ethernet: Тип=128, Номер=0, Длина тела=2, Handle=6
  198. DEBUG RECV: header_net.body_length (network order) = 0x0200 (512)
  199. DEBUG RECV: bodyLenHost (host order) = 2
  200. DEBUG RECV: message.header.body_length после message_to_host_byte_order (должен быть хост) = 2
  201. Получено сообщение через Ethernet: Тип=128, Номер=0, Длина тела=2, Handle=10
  202. Processor (Inst 2): Обработка 'Инициализация канала'
  203. Параметры: LAUVM=0x1, LAK=0x0A (assigned)
  204. SVM (Inst 2): Эмуляция выключения лазера...
  205. Processor (Inst 0): Обработка 'Инициализация канала'
  206. Параметры: LAUVM=0x1, LAK=0x08 (assigned)
  207. SVM (Inst 0): Эмуляция выключения лазера...
  208. Processor (Inst 3): Обработка 'Инициализация канала'
  209. Параметры: LAUVM=0x1, LAK=0x0B (assigned)
  210. SVM (Inst 3): Эмуляция выключения лазера...
  211. Ответ 'Подтверждение инициализации' сформирован (LAK=0x0A).
  212. Ответ 'Подтверждение инициализации' сформирован (LAK=0x0B).
  213. send_protocol_message: Invalid arguments
  214. Sender Thread: Error sending message (type 129) to instance 2 (handle 662693568).
  215. Sender Thread: Deactivating instance 2 (handle 662693568) due to send error.
  216. Ответ 'Подтверждение инициализации' сформирован (LAK=0x08).
  217. Ошибка сегментирования
  218.  
  219.  
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!