[MAS-discuss] Server stability (or: how to kill MAS server in 21 microseconds:-)
Brought to you by:
jcochrane
|
From: Kyku <ky...@os...> - 2006-02-25 15:55:50
|
Hi all,
Suppose the following scenario:
1) open the MAS server in one terminal
2) open command line client in another, connect to the server.
3) pressing Ctrl-C in the client.
In my case, server starts consuming 100% CPU, then prints:
mas: PANIC: unexpected harmful signal ...
mas: system execution failed.
Following is the set of recorded exceptions.
NB: The raised panic may have induced completely inconsistent information:
-------------------------------------------------------------------------------
Class / Object Routine Nature of exception
Effect
-------------------------------------------------------------------------------
MA_SERVER root's creation unexpected harmful signal:
<08351488> Eiffel run-time panic. Bye
-------------------------------------------------------------------------------
MA_SERVER root's creation
<08351488> Routine failure. Bye
-------------------------------------------------------------------------------
MA_SERVER root's creation
<08351488> Routine failure. Bye
-------------------------------------------------------------------------------
MA_SERVER root's creation
<08351488> Routine failure. Bye
-------------------------------------------------------------------------------
mas: dumping core to generate debugging information...
fish: Job 0, 'sudo ./mas -f, 22917 /usr/local/stow/mas/lib/data/*.txt'
terminated by signal SIGABRT (Abort)
Now, when the MAS is consuming 100% CPU, I can hit Ctrl-c in the server
terminal, which starts printing:
Caught signal in main menu:
Broken pipe (13) - continuing ...
Could you please help me with this. Frankly, I consider it a bug - a
server should withstand malicious/bad input from its clients.
---------------------------------------
Darmowe konta email o pojemnosci 500 MB
http://www.free.os.pl
---------------------------------------
|