RE: [reSIProcate] Re: Crash in Stack probe routine
Yes, increasing the stack to 2MB fixes the problem.
Thanks,
CG
Scott Godin
<slgodin@icescape
.com> . To
"'Christian_Gavin@xxxxxxxxxxxx'"
07/18/2005 10:32 <Christian_Gavin@xxxxxxxxxxxx>,
AM resiprocate-devel@xxxxxxxxxxxxxxxxx
rg
cc
Subject
RE: [reSIProcate] Re: Crash in
Stack probe routine
Actually I have seen stack problems on Windows - mainly due to the huge
size
of the Statistics classes.
Dum/test/BasicCall.cxx creates to SipStacks, each with it's own Statistics
stuff. Thus, I need to increase the windows stack reserve size to 2000000.
Another option is to remove the Statistics subsystem, using the #ifdef in
StatisticsManager.hxx
Scott
-----Original Message-----
From: Christian_Gavin@xxxxxxxxxxxx [mailto:Christian_Gavin@xxxxxxxxxxxx]
Sent: Monday, July 18, 2005 1:23 PM
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: [reSIProcate] Re: Crash in Stack probe routine
Hi,
I tried to isolate it too. I added parsing the XML in the small
basicRegister app and it ran fine.
Normally a Windows app has a 1MB stack. Should I increase that?
I doubt parsing a 600 something byte long block of XML would use that much
stack. Hmm.
Christian
----- Message from david Butcher <david@xxxxxxxxxxxxxx> on Fri, 15 Jul 2005
20:29:32 -0400 -----
To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [reSIProcate] Crash in Stack probe routine?
Hi,
I wrote a test against your XML. Parsed just fine.
Your enclosed stack trace isn't all that long; there is no evidence of
excessive
recursion, for example. Is it possible you just need more stack space?
david
_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel