[reSIProcate] Huge usage of stack space for debug builds

[david Butcher]

g++ permits run time allocation of stack. Can we use that here?
For other systems, we could compile time parameterize or pick a small value.

david


On 9/12/05, Scott Godin <slgodin at icescape.com> wrote:
> 
> Good point!
> 
> -----Original Message-----
> From: jason.fischl at gmail.com [mailto:jason.fischl at gmail.com] On Behalf
> Of Jason Fischl
> Sent: Monday, September 12, 2005 2:33 PM
> To: Scott Godin
> Cc: Alan Stokes; resiprocate-devel at list.sipfoundry.org
> Subject: Re: [reSIProcate] Huge usage of stack space for debug builds
> 
> On 9/12/05, Scott Godin <slgodin at icescape.com> wrote:
> > Might be better off with something like 256 or 512, since we are
> logging
> > SIP messages. I assume the there is a memory/performance tradeoff
> here,
> > if we go too small to accommodate most messages.
> 
> Well presumably in any application where performance is a concern
> SipMessages should not be getting logged frequently. I think a smaller
> number makes sense - we shouldn't be optimizing for DEBUG or INFO
> level logging.
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050912/281affa1/attachment.htm>