aboutsummaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorSergey Poznyakoff <gray@gnu.org.ua>2007-04-18 07:33:39 +0000
committerSergey Poznyakoff <gray@gnu.org.ua>2007-04-18 07:33:39 +0000
commit71d23052e4bbb16978a2c38e151d2cbf71320e9d (patch)
tree2022ce3e3ed8b5438ac2b9e0fcd97c88691806a0 /NEWS
parent9a1ddf916e38a3ed89d8d306997efe008a3b95b6 (diff)
downloadmailfromd-71d23052e4bbb16978a2c38e151d2cbf71320e9d.tar.gz
mailfromd-71d23052e4bbb16978a2c38e151d2cbf71320e9d.tar.bz2
Implement stack traces
git-svn-id: file:///svnroot/mailfromd/trunk@1363 7a8a7f39-df28-0410-adc6-e0d955640f24
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS27
1 files changed, 26 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index 3d9c3420..6e68fc69 100644
--- a/NEWS
+++ b/NEWS
@@ -1,2 +1,2 @@
-Mailfromd NEWS -- history of user-visible changes. 2007-04-16
+Mailfromd NEWS -- history of user-visible changes. 2007-04-18
Copyright (C) 2005, 2006, 2007 Sergey Poznyakoff
@@ -84,2 +84,27 @@ settings.
+* Runtime stack traces
+
+New command line option --stack-trace enables dumping stack traces
+on runtime errors. This might help localize the source of the error.
+The trace looks like:
+
+mailfromd: RUNTIME ERROR near ../mflib/match_cidr.mf:30: invalid CIDR (boo%)
+mailfromd: Stack trace:
+mailfromd: 0077: test.mf:7: match_cidr
+mailfromd: 0096: test.mf:13: bar
+mailfromd: 0110: test.mf:18: foo
+mailfromd: Stack trace finishes
+mailfromd: Execution of the configuration program was not finished
+
+Each trace line describes one stack frame, the lines appear in the
+order of most recently called to least recently called. Each frame
+consists of:
+
+1. Value of program counter at the time of its execution
+2. Source code location, if available
+3. Name of the function called
+
+The same output can be obtained by calling function stack_trace()
+in your filter program.
+
* connect handler

Return to:

Send suggestions and report system problems to the System administrator.