From 6913c8b4a49873139750a708178920bb74aeb9d5 Mon Sep 17 00:00:00 2001
From: "Marc G. Fournier" <scrappy@hub.org>
Date: Mon, 11 Nov 1996 11:49:40 +0000
Subject: [PATCH] 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...
---
src/backend/utils/error/assert.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/backend/utils/error/assert.c b/src/backend/utils/error/assert.c
index c100c2e02f6..bdc4f0b0e39 100644
--- a/src/backend/utils/error/assert.c
+++ b/src/backend/utils/error/assert.c
@@ -7,7 +7,7 @@
*
*
* 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
* This should eventually work with elog(), dlog(), etc.
@@ -49,7 +49,10 @@ ExceptionalCondition(char* conditionName,
exceptionP->message, conditionName, detail,
fileName, lineNumber);
}
-
+
+#ifdef ABORT_ON_ASSERT
+ abort();
+#endif
/*
* XXX Depending on the Exception and tracing conditions, you will
* XXX want to stop here immediately and maybe dump core.
--
GitLab