Add an abort() call to ExceptionalCondition so that is Assert is
called, it dumps core... ABORT_ON_ASSERT must be defined, as I don't know if this is the correct way to do this...
This commit is contained in:
parent
9fc64aefe1
commit
6913c8b4a4
|
@ -7,7 +7,7 @@
|
||||||
*
|
*
|
||||||
*
|
*
|
||||||
* IDENTIFICATION
|
* IDENTIFICATION
|
||||||
* $Header: /cvsroot/pgsql/src/backend/utils/error/assert.c,v 1.2 1996/11/11 11:29:15 scrappy Exp $
|
* $Header: /cvsroot/pgsql/src/backend/utils/error/assert.c,v 1.3 1996/11/11 11:49:40 scrappy Exp $
|
||||||
*
|
*
|
||||||
* NOTE
|
* NOTE
|
||||||
* This should eventually work with elog(), dlog(), etc.
|
* This should eventually work with elog(), dlog(), etc.
|
||||||
|
@ -49,7 +49,10 @@ ExceptionalCondition(char* conditionName,
|
||||||
exceptionP->message, conditionName, detail,
|
exceptionP->message, conditionName, detail,
|
||||||
fileName, lineNumber);
|
fileName, lineNumber);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
#ifdef ABORT_ON_ASSERT
|
||||||
|
abort();
|
||||||
|
#endif
|
||||||
/*
|
/*
|
||||||
* XXX Depending on the Exception and tracing conditions, you will
|
* XXX Depending on the Exception and tracing conditions, you will
|
||||||
* XXX want to stop here immediately and maybe dump core.
|
* XXX want to stop here immediately and maybe dump core.
|
||||||
|
|
Loading…
Reference in New Issue