<span style="color: rgb(0, 0, 153);"><span style="font-family: verdana;">Hi Guys,<br>I'm facing a kinda similar problem when compiling my application with Visual Studio 2005 using omniORB4.0.7<br>As soon as the omniORB::Init() function is called, the program crashed, windows returns an Acces violation error.
<br>Did you ever faced this kind of problem?<br><br>Thanks,<br><br>Cheers,<br><br>Tahar<br><br></span></span><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
venson-Hoare" wrote:<br><br>> If the -errlog parameter is supplied the program simply crashes out.<br>> After examining the code it appears that the following line in<br>> omniNames.cc is to blame:<br>><br>
> Line 159: setvbuf(stderr, 0, _IOLBF, 0);<br>><br>> The Visual Studio 2005 documentation states that the 4th argument to<br>> this function, ie size, must be in the range 2 <= size <= INT_MAX<br>> (2147483647). Clearly 0 is not in this range!
<br><br>Sorry for the delay in replying to this. The problem is down to a<br>difference between Windows and Unix platforms. On Unix platforms, the<br>size parameter is the size of the buffer if one is provided, which in<br>
this case there isn't. Windows takes it to be the size of the buffer it<br>should allocate.<br><br>Windows doesn't support line buffering at all, so the code is pointless<br>there anyway. I've fixed it by #ifdefing it away on Windows.
<br><br>Cheers,<br><br>Duncan.<br><br>--<br> -- Duncan Grisby --<br> -- <a href="mailto:duncan@grisby.org">duncan@grisby.org</a> --<br> -- <a href="http://www.grisby.org">http://www.grisby.org</a> --<br><br>
_______________________________________________<br>omniORB-list mailing list<br><a href="mailto:omniORB-list@omniorb-support.com">omniORB-list@omniorb-support.com</a><br><a href="http://www.omniorb-support.com/mailman/listinfo/omniorb-list">
http://www.omniorb-support.com/mailman/listinfo/omniorb-list</a><br></blockquote></div><br>