Ok, I reset my environment, and built 0.25.2 and linked it to my windows
service.
The problem always happens with the socket api, with the function to resolve
hostname
to be exact. Neon is compiled, by default, to use gethostbyname() instead of
getaddrinfo().
Here is the problems during my debugging session:
1- gethostbyname() works fine when the application is run as a normal
console app. But as
soon as I run it as windows service, gethostbyname() always return null. The
function
WSAGetLastError() return error code 10014, and here is the description from
VC about
that error code:
Bad address.
The system detected an invalid pointer address in attempting to use a
pointer argument of a call. This error occurs if an application passes an
invalid pointer value, or if the length of the buffer is too small. For
instance, if the length of an argument, which is a sockaddr structure, is
smaller than the sizeof(sockaddr).
2. So I recompiled neon with the USE_GETADDRINFO flag. The application still
runs fine
as normal console app, but when I run it as windows service, I get a first
exception not handled
problem when the function getaddrinfo() is called.
Now, I really don't get it. The whole thing runs just fine as normal console
app, but as soon
as it is run as windows service, this problem pops up consistently.
If anyone got any success linking neon to a windows service app, could you
please
provide some hint on this issue? I'm using expat 1.95.8, and neon is
compiled with
openssl or zlib.
This is getting me nut. I've spent two whole days on this, something that's
supposed to
be a non-issue.
thanks for any help.
coco
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
_______________________________________________
neon mailing list
[email protected]
http://mailman.webdav.org/mailman/listinfo/neon
