I don't think there is an explicit policy. But I would personally encourage you to look in LLDBAssert.h and consider using the lldbassert() macro defined there In debug builds it behaves like a normal assert But in release builds it dumps a scary assert()-style message with backtrace, but then does not crash. This is helpful because we'd rather much avoid tearing down debug sessions. Of course, you may still end up crashing even if the assert() does not tear us down, but it's at least worth a shot at "ask for bug reports then continue"
Sent from my iPhone > On May 6, 2015, at 11:45 PM, Ilia K <ki.s...@gmail.com> wrote: > > Hello, > > What is our policy about asserts? > > Thanks, > Ilia > _______________________________________________ > lldb-dev mailing list > lldb-dev@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
