CERTI - Patches: patch #8494, Make RTIA to notice if federate...
You are not allowed to post comments on this tracker with your current authentication level.
patch #8494: Make RTIA to notice if federate process crashes in Win32 environment
Submitter: | Timi Tuohenmaa <timit> | ||
Submitted: | Wed 09 Jul 2014 11:03:20 AM UTC | ||
Category: | CERTI | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Attached Files
Depends on the following items
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-06-08 | bussenot | Dependencies | - | ![]() |
Depends on patch #8558 |
2014-07-09 | timit | Attached File | - | ![]() |
Added crash_fix.patch, #31692 |
This patch will make a thread that watches parent process (federate) and triggers when it crashes.
In Windows communication between federate and RTIA is done by tcp-socket and in case of crash socket does not close immediatelly (socket time out takes a very long time). This solves the problem by watching pipe that will be RTIA's stdin. Pipes close on crashes instantly.
More details about this can be seen in thread:
http://lists.nongnu.org/archive/html/certi-devel/2014-07/msg00000.html (watch replies to it too)
This is heavy weight solution that will make RTIA drop in same way as it does in *nix side (when unix socket closes instantly on federate crash).
Lightweight solution would not contain extra socket that triggers in select, but instead thread just runs _exit(EXIT_FAILURE). Both solutions works in practise.