You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Rogério Corrêa (JIRA)" <xe...@xml.apache.org> on 2005/07/26 18:09:22 UTC
[jira] Created: (XERCESC-1467) Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
-----------------------------------------------------------------------------------------------
Key: XERCESC-1467
URL: http://issues.apache.org/jira/browse/XERCESC-1467
Project: Xerces-C++
Type: Bug
Components: Utilities
Versions: 2.5.0
Reporter: Rogério Corrêa
When an exception occurs in the constructor of the class BinHTTPURLInputStream, the socket opened in the call to 'socket' is never closed.
I´m calling closesocket before every throw, but considering a socket object maybe better.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[jira] Commented: (XERCESC-1467) Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
Posted by "Alberto Massari (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1467?page=comments#action_12330684 ]
Alberto Massari commented on XERCESC-1467:
------------------------------------------
Ronald, you are right. I have changed the code to use BinHTTPURLInputStream::closesocket
> Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
> -----------------------------------------------------------------------------------------------
>
> Key: XERCESC-1467
> URL: http://issues.apache.org/jira/browse/XERCESC-1467
> Project: Xerces-C++
> Type: Bug
> Components: Utilities
> Versions: 2.5.0
> Reporter: Rogério Corrêa
>
> When an exception occurs in the constructor of the class BinHTTPURLInputStream, the socket opened in the call to 'socket' is never closed.
> I´m calling closesocket before every throw, but considering a socket object maybe better.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[jira] Commented: (XERCESC-1467) Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
Posted by "Ronald Lamprecht (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1467?page=comments#action_12330677 ]
Ronald Lamprecht commented on XERCESC-1467:
-------------------------------------------
The fix introduces in src\xercesc\util\NetAccessors\WinSock\BinHTTPURLInputStream.cpp line 52 a direct call to function "closesocket" of the wsock32 library. All other access to wsock32 is handled dynamically.
As a result the samples will not link without the additon of "-l wsock32" or an "AC_CHECK_LIB" in configure.ac.
The solution will be of course a dynamic call of "closesocket" in "SocketJanitor::reset()".
The problem was introduced in r231012 on the trunk and is still valid in r290103.
> Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
> -----------------------------------------------------------------------------------------------
>
> Key: XERCESC-1467
> URL: http://issues.apache.org/jira/browse/XERCESC-1467
> Project: Xerces-C++
> Type: Bug
> Components: Utilities
> Versions: 2.5.0
> Reporter: Rogério Corrêa
>
> When an exception occurs in the constructor of the class BinHTTPURLInputStream, the socket opened in the call to 'socket' is never closed.
> I´m calling closesocket before every throw, but considering a socket object maybe better.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: BUILDING XERCES ON SUN8 ULTRA SERVER, USING GCC3.4.2 (libstdc++.6.0.2)
Posted by Sa...@blr.hexaware.com.
Hi
Well, to simplify the matter.
We have sucessfully built Xerces2-6-0 on another machine with different
harware but same OS Version.
That machine has sun4u sparc SUNW,Sun-Fire-480R Architecture and the one
in question is sun4u sparc SUNW,Ultra-4.
Both have the SunOS 5.8 Generic_108528-24.
Should I write to SUN OS mailing list as well????
warm regards
Saurabh
david_n_bertoni@us.ibm.com
08/09/2005 09:51 PM
Please respond to
c-dev@xerces.apache.org
To
c-dev@xerces.apache.org
cc
Subject
Re: BUILDING XERCES ON SUN8 ULTRA SERVER, USING GCC3.4.2 (libstdc++.6.0.2)
> I have build a Xerces 2-6-0, while checking it;s dependencies I see this
> o/p.
>
> It's looking for C++ library for GCC 3.2.3, which doesn't existon ths
> system as we have bootstrapped GCC 3.4.2 over it. it should point to
> libstdc++.6.0.2 for GCC3.4.2.
That seems a pretty dangerous business. Are you sure that will work? My
suspicion is that it will not.
> PLEASE HELP AS WE ARE CLUELESS???
You are asking on the wrong list. I suggest you ask on some GCC-related
list, or read the GCC documentation, as there are ways to build GCC such
that multiple versions can co-exist on the same machine, and that's
probably what you need to do.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Re: BUILDING XERCES ON SUN8 ULTRA SERVER, USING GCC3.4.2 (libstdc++.6.0.2)
Posted by da...@us.ibm.com.
> I have build a Xerces 2-6-0, while checking it;s dependencies I see this
> o/p.
>
> It's looking for C++ library for GCC 3.2.3, which doesn't existon ths
> system as we have bootstrapped GCC 3.4.2 over it. it should point to
> libstdc++.6.0.2 for GCC3.4.2.
That seems a pretty dangerous business. Are you sure that will work? My
suspicion is that it will not.
> PLEASE HELP AS WE ARE CLUELESS???
You are asking on the wrong list. I suggest you ask on some GCC-related
list, or read the GCC documentation, as there are ways to build GCC such
that multiple versions can co-exist on the same machine, and that's
probably what you need to do.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
BUILDING XERCES ON SUN8 ULTRA SERVER, USING GCC3.4.2 (libstdc++.6.0.2)
Posted by Sa...@blr.hexaware.com.
Hi Experts
I have build a Xerces 2-6-0, while checking it;s dependencies I see this
o/p.
It's looking for C++ library for GCC 3.2.3, which doesn't existon ths
system as we have bootstrapped GCC 3.4.2 over it. it should point to
libstdc++.6.0.2 for GCC3.4.2.
PLEASE HELP AS WE ARE CLUELESS???
Attaching the runConfigure(32 bit) we have used. This has been modified
from the original by adding switches for g++ flags.
However it's able to point to the C library(libgcc_s.so.1) correctly.
/user/apradhan/xerces/xerces-c-src_2_6_0/lib >ldd libxerces-c.so
libpthread.so.1 => /usr/lib/libpthread.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libsocket.so.1 => /usr/lib/libsocket.so.1
libgen.so.1 => /usr/lib/libgen.so.1
libstdc++.so.5 => (file not found)
libm.so.1 => /usr/lib/libm.so.1
libgcc_s.so.1 => /tools/remote/gnu/gcc/v3.4.2/lib/libgcc_s.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libc.so.1 => /usr/lib/libc.so.1
libmp.so.2 => /usr/lib/libmp.so.2
libthread.so.1 => /usr/lib/libthread.so.1
/usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1
warm regards
Saurabh
[jira] Resolved: (XERCESC-1467) Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
Posted by "Alberto Massari (JIRA)" <xe...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XERCESC-1467?page=all ]
Alberto Massari resolved XERCESC-1467:
--------------------------------------
Resolution: Fixed
A fix is in SVN. Please verify.
> Socket 's' in the 'BinHTTPURLInputStream' constructor is never closed when an exception occurs.
> -----------------------------------------------------------------------------------------------
>
> Key: XERCESC-1467
> URL: http://issues.apache.org/jira/browse/XERCESC-1467
> Project: Xerces-C++
> Type: Bug
> Components: Utilities
> Versions: 2.5.0
> Reporter: Rogério Corrêa
>
> When an exception occurs in the constructor of the class BinHTTPURLInputStream, the socket opened in the call to 'socket' is never closed.
> I´m calling closesocket before every throw, but considering a socket object maybe better.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org