To get a stack trace, here's one way you could do it:
1) capture a message that causes the fault into a file (strip away any
leading "From " line, but not the "From:" line)
2) reconfigure the build using "--enable-debug --disable-shared"
3) rebuild
4) copy your config file to a new file, and set "Background" to "No" and
"AutoRestart" to "No"
5) load the filter in gdb: "gdb /path/to/new/opendkim"
6) at the gdb prompt: "run -t /path/to/email -x /path/to/modified/conf"
...that should reproduce the assertion failure and leave you at a point
where you can do a "where" to get the stack trace. I might need more
information from you past that, but that will get us started.
-MSK
Received on Wed Sep 08 2010 - 17:42:38 PST
This archive was generated by hypermail 2.2.0+W3C-0.50 : Wed Sep 08 2010 - 20:50:00 PST