< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate] SipStack shutdown crash


I doubt we will ever be merging in the current ares project - I think we
have too many branched changes to make this realistic.  We should
probably just be looking at backporting fixes.

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Daniel Pocock
> Sent: Friday, September 08, 2006 5:54 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate] SipStack shutdown crash
> 
> 
> 
> Scott Godin wrote:
> 
> >I don't see this problem, but if you can confirm that initializing
the
> >variables fixes the problem for you and can provide a patch - then I
> >can commit a patch to SVN.
> >
> >
> >
> 
> It is crashing at free(channel->lookups)
> 
> channel->lookups is a valid pointer to a string created by strdup
> 
> Maybe there is something odd about the way strdup gets heap space
> 
> Commenting out free(channel->lookups) eliminates the issue but causes
> memory leakage.
> 
> Is it likely that someone will be updating the entire contrib/ares
tree
> before reSIProcate 1.0 comes out, or should we be looking at
> backporting fixes/patching the version of ares that is already
present?
> 
> 
> >Thanks,
> >
> >Scott
> >
> >
> >
> >>-----Original Message-----
> >>From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >>[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> >>Daniel Pocock
> >>Sent: Thursday, September 07, 2006 11:59 AM
> >>To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> >>Subject: Re: [reSIProcate] SipStack shutdown crash
> >>
> >>
> >>
> >>Daniel Pocock wrote:
> >>
> >>
> >>
> >>>I've been evaluating some reSIProcate based code on the Windows
> >>>
> >>>
> >>platform.
> >>
> >>
> >>>When I delete the SipStack object (after DUM is shutdown and
deleted
> >>>properly), the Ares code complains about an invalid pointer.  This
> >>>always happens at the same place.
> >>>
> >>>Note that this only seems to occur with the release version and not
> >>>
> >>>
> >>the
> >>
> >>
> >>>debug build.
> >>>
> >>>
> >>>
> >>>
> >>I notice in the more recent ares code that they initialise all the
> >>pointers to NULL at init time:
> >>
> >>
> >>http://cool.haxx.se/cvs.cgi/curl/ares/ares_init.c?rev=1.38&content-
> >>type=text/vnd.viewcvs-markup
> >>
> >>but the version of ares in reSIProcate doesn't have those changes.
> >>
> >>
> >>
> >>
> >>>Does anyone have any ideas?
> >>>
> >>>   ntdll.dll!7c901230()
> >>>
> >>>
> >>>
> >>>
> >>>>> ntdll.dll!7c96c943()
> >>>>> ntdll.dll!7c96cd80()
> >>>>> ntdll.dll!7c960af8()
> >>>>> ntdll.dll!7c960bcc()
> >>>>> kernel32.dll!7c85e9cf()
> >>>>> msvcr71d.dll!_CrtIsValidHeapPointer(const void *
> >>>>>pUserData=0x007b5e30)  Line 1807 C
> >>>>> msvcr71d.dll!_free_dbg_lk(void * pUserData=0x007b5e30, int
> >>>>>nBlockUse=0x00000001)  Line 1132 + 0x9   C
> >>>>> msvcr71d.dll!_free_dbg(void * pUserData=0x007b5e30, int
> >>>>>nBlockUse=0x00000001)  Line 1070 + 0xd   C
> >>>>> msvcr71d.dll!free(void * pUserData=0x007b5e30)  Line 1025 + 0xb
> >>>>>
> >>>>>
> >C
> >
> >
> >>>>> gencc_sip.dll!_ares_destroy_internal()  + 0x69  C
> >>>>> gencc_sip.dll!_ares_destroy_suppress_callbacks()  + 0xc C
> >>>>> gencc_sip.dll!resip::AresDns::~AresDns()  Line 114 + 0xf
> >>>>> gencc_sip.dll!resip::AresDns::`scalar deleting destructor'()  +
> >>>>>0x8
> >>>>> gencc_sip.dll!resip::DnsStub::~DnsStub()  Line 76
> >>>>> gencc_sip.dll!resip::DnsStub::`vector deleting destructor'()  +
> >>>>>0x8
> >>>>> gencc_sip.dll!resip::SipStack::~SipStack()  + 0x98      C++
> >>>>> gencc_sip.dll!resip::SipStack::`scalar deleting destructor'()  +
> >>>>>0x8      C++
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>_______________________________________________
> >>>resiprocate-devel mailing list
> >>>resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> >>>https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >>>
> >>>
> >>>
> >>>
> >>_______________________________________________
> >>resiprocate-devel mailing list
> >>resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> >>https://list.sipfoundry.org/mailman/listinfo/resiprocate-deve
> >>
> >l
> >
> >
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel