> + Make the program fail, without creating a core file.
> + abort() will send SIGABRT which (most likely) generates core.
> + Use SIGKILL instead, which cannot be caught.
> + An alternative would be to use _exit(EXIT_FAILURE),
> + but then valgrind would report lots of memory leaks.
> + */
> +#ifdef __WIN__
> +#define DBUG_SUICIDE() DBUG_ABORT()
> +#define DBUG_SUICIDE() (_db_flush_(), kill(getpid(), SIGKILL))
Verified on linux, but since I don't have a Win-box I'll rather ask a stupid
question. Does ^ mean that dbug_suicide will do what dbug_abort did before (dump
cores) on win-platforms?
Jørgen Løland | Senior Software Engineer | +47 73842138