I agree with Neil. You could also support a release-with-debug build, something that's optimized but still supports debugging macros. That way, if someone encounters a bug due to optimization, they at least will have traces available to them.
On Fri, May 20, 2011 at 5:43 AM, Neil Gierman <ngier...@roadrunn.com> wrote: > > On May 20, 2011 7:38 AM, "Daniel Stenberg" <dan...@haxx.se> wrote: >> >> Hi friends, >> >> I've been thinking about libssh2's ability to provide detailed traces when >> built with --enable-debug. It is a very useful feature and we ask for such >> traces almost at once for just about every bug report we get. >> >> How about we enable the trace feature for all builds unconditionally? It >> will take away the huge hurdle for people that has to rebuild the lib etc >> and it will better allow apps to also be able to ask libssh2 to provide >> tracing etc. >> >> There might be some very minor performance penalties involved but we can >> probably make sure they are very small. I still think the gain in >> convenience will compensate more than enough. >> >> Any opinions, thoughts or other feedback? >> >> -- >> >> / daniel.haxx.se >> _______________________________________________ >> libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel > > I personally would like to keep it just for debug builds. I would really > rather not have any extra debugging information compiled in the release > builds even if it is only sitting dormant. > > _______________________________________________ > libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel > > _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
