Thread: [OpenSIPStack] ATLSIPLib and Interop.AxATLSIPLib
Brought to you by:
joegenbaclor
From: Whit T. <de...@wh...> - 2007-08-13 17:50:48
|
This is a question related to the problems I've been having with the ntdll.dll crash. I just want to ensure that I am using the correct libraries and installing everything correctly. When I compile ATLSIP in Release, it generates the ATLSIP.dll When I compile ATLSIP in Release-Minimal mode, it generates the AxInterop.ATLSIPLib.1.0.dll file in the Release folder, hover its timestamp is when I first downloaded ATLSIP out of CVS, so I'm assuming this isn't compiled, but copied. Which library should be used in a .NET app as a reference? Should you import the ATLSIP.dll directly, or should you use the Interop library? Hopefully there is no such thing as a 'dumb' question! Regards, Whit |
From: Ilian J. C. P. <ip...@so...> - 2007-08-14 05:21:08
|
Hello Whit, No such thing as a dumb question. :) Whit Thiele wrote: > > This is a question related to the problems I've been having with the > ntdll.dll crash. I just want to ensure that I am using the correct libraries > and installing everything correctly. > > > When I compile ATLSIP in Release, it generates the ATLSIP.dll > > When I compile ATLSIP in Release-Minimal mode, it generates the > AxInterop.ATLSIPLib.1.0.dll file in the Release folder, hover its timestamp > is when I first downloaded ATLSIP out of CVS, so I'm assuming this isn't > compiled, but copied. > It is compiled but not always. The Interop DLLs are there for interoperability between .NET and Win32/ATL. So if there are no major structural changes to ATLSIP, they don't need to compiled. Just check if your AxInterop.ATLSIPLib.1.0.dll and Interop.ATLSIPLib.1.0.dll of your Release and Interop folders have the same timestamps. Also, one quirk I found with VS is that it doesn't always automatically copy Interop.ATLSIPLib.1.0.dll to the target folder. You may have to manually copy this to your Release folder. > > Which library should be used in a .NET app as a reference? Should you import > the ATLSIP.dll directly, or should you use the Interop library? > You should only add ATLSIP as a reference. VS will take care of the rest. - Ilian > > Hopefully there is no such thing as a 'dumb' question! > > > Regards, > > Whit > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > |
From: Yacine A. <yac...@ms...> - 2007-08-14 09:44:52
|
Hello Ilian, I have sent the sip.log file, have you find something? I'm still having crashes. > Date: Tue, 14 Aug 2007 13:21:10 +0800 > From: ip...@so... > To: ope...@li... > Subject: Re: [OpenSIPStack] ATLSIPLib and Interop.AxATLSIPLib >=20 > Hello Whit, >=20 > No such thing as a dumb question. :) >=20 > Whit Thiele wrote: > > > > This is a question related to the problems I've been having with the > > ntdll.dll crash. I just want to ensure that I am using the correct libr= aries > > and installing everything correctly. > > > > > > When I compile ATLSIP in Release, it generates the ATLSIP.dll > > > > When I compile ATLSIP in Release-Minimal mode, it generates the > > AxInterop.ATLSIPLib.1.0.dll file in the Release folder, hover its times= tamp > > is when I first downloaded ATLSIP out of CVS, so I'm assuming this isn'= t > > compiled, but copied. > > =20 > It is compiled but not always. The Interop DLLs are there for=20 > interoperability between .NET and Win32/ATL. So if there are no major=20 > structural changes to ATLSIP, they don't need to compiled. Just check if= =20 > your AxInterop.ATLSIPLib.1.0.dll and Interop.ATLSIPLib.1.0.dll of your=20 > Release and Interop folders have the same timestamps. >=20 > Also, one quirk I found with VS is that it doesn't always automatically=20 > copy Interop.ATLSIPLib.1.0.dll to the target folder. You may have to=20 > manually copy this to your Release folder. > > > > Which library should be used in a .NET app as a reference? Should you i= mport > > the ATLSIP.dll directly, or should you use the Interop library? > > =20 > You should only add ATLSIP as a reference. VS will take care of the rest. >=20 > - Ilian > > > > Hopefully there is no such thing as a 'dumb' question! > > > > > > Regards, > > > > Whit > > > > > > > > > > -----------------------------------------------------------------------= -- > > This SF.net email is sponsored by: Splunk Inc. > > Still grepping through log files to find problems? Stop. > > Now Search log events and configuration files using AJAX and a browser. > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > _______________________________________________ > > opensipstack-devel mailing list > > ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel > > > > > > =20 >=20 >=20 > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > opensipstack-devel mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel _________________________________________________________________ Essayez Live.com, votre nouvelle page d'accueil ! Personnalisez-la en quelq= ues clics pour retrouver tout ce qui vous int=E9resse au m=EAme endroit. http://www.live.com/getstarted= |
From: Ilian J. C. P. <ip...@so...> - 2007-08-14 12:03:36
|
Hi Yacine, Yacine Auczone wrote: > Hello Ilian, > I have sent the sip.log file, have you find something? > I'm still having crashes. > I can't tell directly from your logs what's causing your problem. And I still can't reproduce this, unfortunately. Can you do the following again? 1. Make sure that your OpenSIPStack code is up-to-date 2. Rebuild ATLSIP (clean all dlls first; atlsip.dll, *interop dlls) 3. Rebuild OSSPhone (you may have to manually add references to AxInterop and Interop dlls) Also, may I know a few more details how to bug occurs? Like how many calls before the crash, the length of the calls, the settings you set in OSSPhone, etc. Does this occur also in Debug build? If so, can your debugger attach to it and see where the crash comes from? Whit, I take back what I said earlier: "You should only add ATLSIP as a reference. VS will take care of the rest." For some reason, VS *sometimes* doesn't automatically load the AxInterop dll. You may have to manually add this. Make sure all the references to the *Interop dlls are up-to-date. Regards, Ilian > <snip> |