Home » U++ Library support » U++ Library : Other (not classified elsewhere) » Segfaults with One container?
| Re: Segfaults with One container? [message #23177 is a reply to message #23172] |
Wed, 23 September 2009 09:22   |
phirox
Messages: 49
Registered: December 2007
|
Member |
|
|
Thank you for your fast response, and as always it was right on. I think I have stared to long at the problem to notice it myself 
For future references the solution for me was to add the following code:
s.Init();
One<Socket::Data> data = new Socket::Data;
s.Attach(data);
The reason for all of this; under *nix when you fork() or reload your own or other program with exec() all sockets are inherited. So for example by just adding in the above example you can continue working on it without interruption. Maybe an idea to add this feature as a function OldSocket/OpenedSocket besides the existing ClientSocket and ServerSocket?
[Updated on: Wed, 23 September 2009 13:45] Report message to a moderator |
|
|
|
Current Time: Tue May 14 12:51:52 CEST 2024
Total time taken to generate the page: 0.02719 seconds
|
Members
Pages
Help
Register
Login
Home
