a few FIXMEs

git-svn-id: https://www4.informatik.uni-erlangen.de/i4svn/danceos/trunk/devel/fail@1036 8c4709b5-6ec9-48aa-a5cd-a96041d1645a

core/SAL/SimulatorController.hpp

@@ -231,6 +231,7 @@ class SimulatorController
 		 * @param ev the event pointer to be added
 		 * @return the pointer of the occurred event (it is not guaranteed that
 		 *         this pointer will be equal to ev)
+		 * FIXME rename to make clear this returns when *any* event occurs
 		 */
 		fi::BaseEvent* addEventAndWait(fi::BaseEvent* ev);
 		/**

core/controller/CoroutineManager.cc

@@ -13,6 +13,7 @@ void CoroutineManager::m_invoke(void* pData)
 {
 	//std::cerr << "CORO m_invoke " << co_current() << std::endl;
 	reinterpret_cast<ExperimentFlow*>(pData)->coroutine_entry();
+	//m_togglerstack.pop(); // FIXME need to pop our caller
 	co_exit(); // deletes the associated coroutine memory as well
 
 	// we really shouldn't get here

core/plugins/tracing/TracingPlugin.hpp

@@ -23,6 +23,8 @@
  * FIXME: more explicit startup/shutdown; listener-based event interface needed?
  *        -> should simulator.removeFlow make sure all remaining active events
  *           are delivered?
+ * FIXME: trace a sequence of pb messages, not a giant single one (pb weren't
+ *        made for huge messages)
  */
 class TracingPlugin : public fi::ExperimentFlow
 {