Re: [reSIProcate] resiprocate stack memeory leak?????

[Byron Campen <bcampen@xxxxxxxxxxxx>]

        I see it in Fifo.hxx.

Best regards,
Byron Campen

> Where do you see mSize being set to NoSize?
>
> On 9/21/06, FrankYuan <frankyuan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > My question why NoSize(0U-1)  is used for mSize when clear func is  
> > called.
> >
> > mStateMachineFifo.size() may return either 0 or NoSize if the  
> > queue is
> > empty.
> >
> > It should alway return 0 if the queue is empty and NoSize should  
> > not be
> > used.
> >
> > NoSize causes confusion and is error prone.
> >
> > Thanks
> >
> > Frank Yuan
> > Emergent-Netsolutions.com
> > 972-359-6600
> >
> >
> >
> > Jason Fischl wrote:
> > > On 9/20/06, Byron Campen <bcampen@xxxxxxxxxxxx> wrote:
> > > >         As for your questions about AbstractFifo, I am unsure why
> > > > mSize is
> > > > needed. Can anyone answer this (or, answer why clear is a no-op)?
> > >
> > > The clear method is virtual and gets defined in the subclasses.
> > >
> > > I believe that mSize is there as an optimization.
> > _______________________________________________
> > 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-devel

Attachment: smime.p7s
Description: S/MIME cryptographic signature