Boost C++ Libraries: Ticket #5156: copying opened socket between processes (Microsoft Windows)

component changed; owner set

Mateusz Loskot — Fri, 18 Feb 2011 21:33:12 GMT

owner set to chris_kohlhoff
component None → asio

I believe it's not a confirmed bug and seems you are unsure as well. This is a question which belongs to boost-users mailing list. I would suggest to close as invalid.

BTW, next time you will be reporting ticket, it's a good idea to select component/library corresponding to problem being reported.

irol@… — Fri, 18 Feb 2011 21:37:26 GMT

Well, I'm quite sure that this code throws an exception. Best Regards, Irek Olchawski.

Mateusz Loskot — Fri, 18 Feb 2011 21:49:17 GMT

Exception thrown does not necessarily mean there is a bug.

irol@… — Fri, 18 Feb 2011 22:21:28 GMT

If it is not a bug why it throws ? Maybe you should change documentation. Let say: 'socket::assign throws an exception. Catch it and ignore'

Mateusz Loskot — Fri, 18 Feb 2011 22:57:02 GMT

Certainly, the socket::assign can throw on error. No need to change the documentation. I'm not saying it is not a bug. I'm suggesting an exception is a perfectly valid situation and the fact an exception is thrown does not necessarily mean it is caused by a bug.

Nevertheless, similar more complete report have been submitted here #5157

Irek Olchawski — Sat, 19 Feb 2011 06:52:44 GMT

Replying to mloskot:

Certainly, the socket::assign can throw on error. No need to change the documentation. I'm not saying it is not a bug. I'm suggesting an exception is a perfectly valid situation and the fact an exception is thrown does not necessarily mean it is caused by a bug.

Next strange thing is that If you ignore exception everything works fine. I can use assigned socket to communication.

Nevertheless, similar more complete report have been submitted here #5157

I read this. Exactly the same like mine.