X-Git-Url: http://bilbo.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/149c63f36e15b8500b1e826bda5138318ff7ba2b..8d62bb541920e2e4e0f7d1fa26a7f6eec79370c2:/include/xbt/asserts.h diff --git a/include/xbt/asserts.h b/include/xbt/asserts.h index 5372224543..455e30883a 100644 --- a/include/xbt/asserts.h +++ b/include/xbt/asserts.h @@ -1,6 +1,6 @@ /* xbt/asserts.h -- assertion mechanism */ -/* Copyright (c) 2005-2020. The SimGrid Team. All rights reserved. */ +/* Copyright (c) 2005-2023. The SimGrid Team. All rights reserved. */ /* This program is free software; you can redistribute it and/or modify it * under the terms of the license (GNU LGPL) which comes with this package. */ @@ -8,9 +8,9 @@ #ifndef XBT_ASSERTS_H #define XBT_ASSERTS_H -#include +#include +#include #include -#include SG_BEGIN_DECL XBT_PUBLIC_DATA int xbt_log_no_loc; /* Do not show the backtrace on failed backtrace when doing our tests */ @@ -19,20 +19,38 @@ XBT_PUBLIC void xbt_backtrace_display_current(); /** * @addtogroup XBT_error + * + * @{ + */ +/** @brief Kill the program in silence */ +XBT_ATTRIB_NORETURN XBT_PUBLIC void xbt_abort(void); + +/** + * @brief Kill the program with an error message + * @param ... a format string and its arguments + * + * Things are so messed up that the only thing to do now, is to stop the program. + * + * The message is handled by a CRITICAL logging request, and may consist of a format string with arguments. + */ +#define xbt_die(...) \ + do { \ + XBT_CCRITICAL(root, __VA_ARGS__); \ + xbt_abort(); \ + } while (0) + +/** * @brief Those are the SimGrid version of the good ol' assert macro. * * You can pass them a format message and arguments, just as if it where a printf. * It is converted to a XBT_CRITICAL logging request. - * Be careful: the boolean expression that you want to test should not have side effects, because assertions are - * disabled at compile time if NDEBUG is set. + * An execution backtrace is also displayed, unless the option --log=no_loc is given at run-time. * - * @{ + * Unlike the standard assert, xbt_assert is never disabled, even if the macro NDEBUG is defined at compile time. So + * it's safe to have a condition with side effects. */ -#ifdef NDEBUG -#define xbt_assert(...) ((void)0) -#else - /** @brief The condition which failed will be displayed. - @hideinitializer */ +/** @brief The condition which failed will be displayed. + @hideinitializer */ #define xbt_assert(...) \ _XBT_IF_ONE_ARG(_xbt_assert_ARG1, _xbt_assert_ARGN, __VA_ARGS__)(__VA_ARGS__) #define _xbt_assert_ARG1(cond) _xbt_assert_ARGN((cond), "Assertion %s failed", #cond) @@ -45,7 +63,6 @@ XBT_PUBLIC void xbt_backtrace_display_current(); abort(); \ } \ } while (0) -#endif /** @} */ SG_END_DECL