I've not got to the bottom of what's causing the error, but have now tried gcc4 on it with the same results, and tried to compile it with Sun Studio; this compiled, but is giving weird runtime link errors.
So; I've exploded out the iovec structure into a simple char* buffer and am just using plain 'write' to send the command to the rtpproxy process - success. Must be a Solaris specific problem with the way OpenSIPS creates the FD's to the proxy process amongst the threads. Anyway - I'm moving forward again - just need to work out why the rtpproxy process returns 'port 0' in the reply. A voyage of discovery :-) Can any of the developers see a reason why exploding the iovec structure into a simple buffer is going to give me problems in the future? Can't see this being a heavily performance centric bit of the code - the media path is probably the important bit. Looks as if using iovec and writev is just an easy way to code up multiple arguments to pass to the proxy process. Lastly, if anyone is interested in the patch, let me know where to send it. m ----- Marty Lee e: [email protected] Technical Director v: +44 845 869 2661 Maui Systems Ltd f: +44 871 433 8922 Scotland, UK w: http://www.maui-systems.co.uk _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
