From: SourceForge.net <no...@so...> - 2013-03-24 16:15:47
|
Bugs item #3608957, was opened at 2013-03-24 09:15 Message generated for change (Tracker Item Submitted) made by sbron You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3608957&group_id=10894 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: 01. Notifier Group: current: 8.6.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Schelte Bron (sbron) Assigned to: Kevin B KENNY (kennykb) Summary: Events posted by Tcl_QueueEvent linger in queue Initial Comment: My C library posts an event via Tcl_QueueEvent when the app receives a signal (like SIGHUP). When using the library with a non-threaded tclsh, the event is picked up by the event loop and processed almost immediately. However, with a threaded tclsh nothing happens until some other event occurs. At that time the queued events and the other event are all processed. Is this the intended behavior? Issue found on OpenSUSE 12.3 (linux 3.7.10) 64-bit. I have attached the stripped down sources for a library that reproduces the problem. Run the script and send a SIGHUP to the process. Observe that with a non-threaded tclsh the script reports "signal" immediately. With a threaded tclsh the "signal" report comes out just before the "Boo!". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3608957&group_id=10894 |