Hmm... I wonder if any needed code has creeped in wrapped around asserts.... or the compile options for the release target may not be quite in sync with those for debug...
On 7/11/07, Alexey Trizno <[EMAIL PROTECTED]> wrote:
> On 7/11/07, Alexey Trizno <[EMAIL PROTECTED]> wrote: > > I tried to use release-version of sipXtapi.dll compiled from latest revision > > (using VS2005), but it still crash with access violation, when I call some > > phone number :( Debug version works fine. > > It is likely caused by use of uninitialized variable somewhere inside sipXtapi. > So, log is useless here. If you're able to reproduce this you could use some > memory checker (BoundsChecker or so) and see, where does this occur. > > Patches, fixing uses of uninitialized variables are always welcome. hmmm... only my sipXtapi release version crash? hmm. -- Best regards, Alexey [ [EMAIL PROTECTED] ] _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
-- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
