>> I think we should have a discussion about the all the asserts. >> I've never worked on a project that keeps asserts in the release build. >> They are more of a development tool. >> They make the code bigger, slower, and they are confusing to users. > > It depends on the potential of breakage of the software. > > In parted we have it enabled by default however it can *corrupt* your > disk if something goes wrong. Many vendors disable it then. > > I think we could do it different. For GIT versions (not tagged) enable > it by default and for released versions disable it by default.
Yes, I think they must be turned off for release builds. Since this is now a multi session library, you don't want an assert in one session dumping them all. If you use libfreerdp as an xrdp module, one session can kill the whole server, even sessions not using libfreerdp. Jay ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Freerdp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freerdp-devel
