[sldev] Finding memory leaks in VS2003

[Able Whitman]

As a quick update, I have not been able to successfully build a VS8 Debug
configuration for the 1.17.2.0 release, either. It could be that there is a
simple fix, but a debug build takes so long on my poor machine that I just
haven't taken the time to get to the root of the problem.

I've been making due with a ReleaseNoOpt build for my own development, which
unfortunately isn't suitable for leak finding.

--Able

On 6/29/07, Nicholaz Beresford <nicholaz at blueflash.cc> wrote:
>
>
> Umm, of course the subject should be VS2003, I'm not sure
> if Debug builds work under VS2005 (see Able's recents posts
> about this).
>
>
> Nick
>
>
>
> Nicholaz Beresford wrote:
> >
> > Based on a suggestion from Bryan I added my patch and knowledge about
> > finding memory leaks to the wiki and the contrib box:
> > https://wiki.secondlife.com/wiki/Finding_leaks
> >
> > Feel free to explore, expand or discuss there.
> >
> >
> >
> > Nick
> >
> > _______________________________________________
> > Click here to unsubscribe or manage your list subscription:
> > /index.html
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20070629/4b803a33/attachment-0001.htm