[Lldb-commits] [lldb] r231310 - Introduce lldbassert(x)

[Zachary Turner]

BTW, I have just uploaded http://reviews.llvm.org/D8068 to LLVM which
implements backtracing of self on Windows (previously only backtracing of
other threads was supported).  So once that goes through, if we switch this
code to using llvm::sys::PrintBacktrace(), we should have a standard
backtrace format across all platforms that LLVM supports.

I like this feature now that I understand the use case, thanks for
introducing it.

On Wed, Mar 4, 2015 at 3:31 PM Siva Chandra <sivachandra at google.com> wrote:

> On Wed, Mar 4, 2015 at 2:59 PM, Enrico Granata <egranata at apple.com> wrote:
> > +#ifdef LLDB_CONFIGURATION_DEBUG
> > +#define lldbassert(x) assert(x)
> > +#else
> > +#define lldbassert(x) lldb_private::lldb_assert(x, #x, __FUNCTION__,
> __FILE__, __LINE__)
> > +#endif
>
> Why should we have this ifdef? As in, why shouldn't we use lldb_assert
> unconditionally, always (giving us the benefit of backtraces always)?
> _______________________________________________
> lldb-commits mailing list
> lldb-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150305/dfbe88a1/attachment.html>