|
|
|
||||||
|
I love IceBox's simplicity and powerful features.But when a uncatched exception occured(such as a bad pointer,or s segment fault,signal 11 etc...),all services will end up with the IceBox process. Even if I catch it and just exit the thread which the exception throws from,I find Ice run-time can not restart a new thread to keep the available thread pool size. So I suggest that IceBox can make the services or threads more independent with each other.
__________________
Yunqiao Yin Baosteel real-time process control ICE中文论坛http://lingdoo.just.as 欢迎大家捧场 |
|
||||||
|
Quote:
__________________
Yunqiao Yin Baosteel real-time process control ICE中文论坛http://lingdoo.just.as 欢迎大家捧场 |
|
||||||
|
Yes, that's not really possible. All threads co-exist in the same memory space so they can all overwrite each other and do other bad things if they are buggy.
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| GridRegistry reliability | sinofool | Help Center | 1 | 10-30-2006 11:55 PM |
| Reliability, Footprint & Portability | prakashbuddhira | Help Center | 1 | 04-03-2006 06:36 AM |
| IceStorm "batch" reliability with Java? | SteveWampler | Help Center | 3 | 10-27-2005 02:54 PM |
| a thread problem | fw_csha | Help Center | 2 | 05-15-2005 06:41 AM |
| Ice::Thread and GUI with Qt | catalin | Help Center | 5 | 09-08-2004 11:20 AM |