11-23-2012, 12:17 AM
Assertions are exactly for debugging - they are operations that verify that things are what the programmer assumes them to be, but these checks are too costly to perform in runtime. Instead, it is expected that the developers catch all of their occurences in debug mode. That's why they don't appear in release mode.
Can you post a gdb stack trace of such an assert? I'm very interested in what the circumstances were when it happenned.
The library upgrades look useful enough (and most importantly, not-breaking-anything enough
), so I'll integrate them when I have time. Or ask FakeTruth to give you write access to the svn 
Can you post a gdb stack trace of such an assert? I'm very interested in what the circumstances were when it happenned.
The library upgrades look useful enough (and most importantly, not-breaking-anything enough
), so I'll integrate them when I have time. Or ask FakeTruth to give you write access to the svn