cored throw exception when quickly stop and start emulation

[GoogleCodeExporter]

What steps will reproduce the problem?
1. install cast svn 418 or newer after install CORE 1597 or newer.
2. start cored and core client,add two routers connected with a link from core 
GUI.
3. start and stop emulation by clicking the ŕun'button on GUI quickly until an 
error message pops up.

What is the expected output? What do you see instead?
ls -ld /tmp/pycore.* shows different permission of /tmp/pycore.<sid>/ 
directory. Normally cases are <uid> <root>. Error case is <root> <root>. See 
output below:
-------------------------------------------
yueli@foxtrot:~$ ls -dl /tmp/pycore.46243/
drwxrwxrwx 4 yueli root 4096 Mar 22 13:55 /tmp/pycore.46243/
yueli@foxtrot:~$ ls -dl /tmp/pycore.46243/
drwxrwxrwx 4 yueli root 4096 Mar 22 13:55 /tmp/pycore.46243/
yueli@foxtrot:~$ ls -dl /tmp/pycore.46243/
ls: cannot access /tmp/pycore.46243/: No such file or directory
yueli@foxtrot:~$ ls -dl /tmp/pycore.*
drwxrwxrwx 4 yueli root 4096 Mar 22 13:56 /tmp/pycore.46244
yueli@foxtrot:~$ ls -dl /tmp/pycore.*
drwxrwxrwx 4 yueli root 4096 Mar 22 13:56 /tmp/pycore.46245
yueli@foxtrot:~$ ls -dl /tmp/pycore.*
drwxrwxrwx 4 yueli root 4096 Mar 22 13:56 /tmp/pycore.46245
drwxrwxrwx 2 root  root 4096 Mar 22 13:56 /tmp/pycore.46246
----------------------------------------------------------------

There is an exception found in /var/log/cored.log - see attachment.

What version of the product are you using? On what operating system?
CORE svn 1597-1600 
linux 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

Please provide any additional information below.

Original issue reported on code.google.com by yueli.y...@gmail.com on 22 Mar 2013 at 9:29

Attachments:

• cored.log

[GoogleCodeExporter]

fixed exception in r734, error message will be printed for broken pipes

directory permission issue still needs resolution

Original comment by ahrenh...@gmail.com on 25 Mar 2013 at 3:46

• Changed state: Started

[GoogleCodeExporter]

closed bug because issue described in subject line has been fixed

Original comment by ahrenh...@gmail.com on 27 Mar 2013 at 3:49

• Changed state: Fixed