int main(int argc, char *argv[])
{
    char *buf=NULL;buf[0]=0;
    return 0;
}

#include <thread>

void intentionalCrash()
{
    auto noop = [](){return;};
    // Thread t1 is in a joinable state.
    // When program returns t1 will be out of scope.
    // Destructing a joinable thread creates a crash.
    std::thread t1(noop);
}

int main()
{
    intentionalCrash();
    return 0;
}

你可以在c++代码中使用汇编，但是INT 3只适用于x86系统，其他系统可能有其他的陷阱/断点指令。

int main()
{
    __asm int 3;

    return 0;
}

INT 3导致中断并调用由OS设置的中断向量。

int main(int argc, char *argv[])
{
    char *buf=NULL;buf[0]=0;
    return 0;
}

写入只读内存会导致分割错误，除非你的系统不支持只读内存块。

int main() {
    (int&)main = 0;
}

我在Windows 7上用MingGW 5.3.0测试了它，在Linux Mint上用GCC测试了它。我认为其他编译器和系统也会有类似的效果。

答案是平台特定的，取决于你的目标。但这里是Mozilla Javascript崩溃函数，我认为这说明了很多挑战，使这个工作:

static JS_NEVER_INLINE void
CrashInJS()
{
    /*
     * We write 123 here so that the machine code for this function is
     * unique. Otherwise the linker, trying to be smart, might use the
     * same code for CrashInJS and for some other function. That
     * messes up the signature in minidumps.
     */

#if defined(WIN32)
    /*
     * We used to call DebugBreak() on Windows, but amazingly, it causes
     * the MSVS 2010 debugger not to be able to recover a call stack.
     */
    *((int *) NULL) = 123;
    exit(3);
#elif defined(__APPLE__)
    /*
     * On Mac OS X, Breakpad ignores signals. Only real Mach exceptions are
     * trapped.
     */
    *((int *) NULL) = 123;  /* To continue from here in GDB: "return" then "continue". */
    raise(SIGABRT);  /* In case above statement gets nixed by the optimizer. */
#else
    raise(SIGABRT);  /* To continue from here in GDB: "signal 0". */
#endif
}