|
|
|
|||||
|
python: uncatchable Exception 'Ice::CommunicatorDestroyedException'
Hi,
when the communicator is destroyed, a later acess to a proxy (concrete: str(proxy)) leads to SIGABRT. "terminate called after throwing an instance of 'Ice::CommunicatorDestroyedException'" Is this a bug, unfortunately wanted or is their a way prevent ICE from killing the application? Thanks, Matthias P.S: linux 2.6.16, Ice 3.0.1, python 2.4 |
![]() |
| 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 |
| Have IceUtil::Exception inherit from std::exception? | bpolivka | Comments | 2 | 12-13-2006 11:52 AM |
| Python | BiT | Help Center | 1 | 09-19-2006 06:21 PM |
| pb with python example | arnaud | Help Center | 13 | 03-06-2006 03:36 AM |
| Ice for Python | davidcr1983 | Help Center | 3 | 07-27-2005 01:01 PM |
| about python and icestorm | code | Help Center | 2 | 12-06-2004 12:08 PM |