I'm not sure if you are referring to SF or O'scope as the "application", but one exiting probably triggers the other so maybe it doesn't matter...
I would start by searching the relevant source for components of that message string, probably in a catch block. Failing that I would then run the program in a debugger set to catch that exception and see where it lands. Somebody probably put an exit() there thinking there was no more to do, or perhaps didn't bother to catch the exception at all (although the message doesn't look like a default). There is a tendency in TOS to put exits in "library classes", so it might be buried in the message handling packages. MS Rémi Villé wrote: > Hi, > > I use TOSSIM with SerialForwarder(in the python script) and the java > Oscilloscope application modified. > When the simulation ends it make the java application stop too > (s...@localhost:9002 died - exiting (java.io.IOException: end-of-stream)). > I don't want the java app exit, to close some files or compute something > before the end for example. > > Is there a simple way to do that ? or must I modify tinyos.jar ? and > what class is concerned ? > > Thanks, > > Rémi > > > ------------------------------------------------------------------------ > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
