In my experience claws-mail's crash dialog causes more problems than it solves.
The stack trace is usually bogus, can't be generated or claws-mail simply becomes unresponsive instead of properly creating a core dump that would actually be useful.
In case of claws-mail 3.9.0 "killall -SIGSEGV claws-mail" merely causes the
following console messages to appear:
claws.c:102:Starting Claws Mail version Claws Mail 3.9.0
main.c:2378:another Claws Mail instance is already running.
No dialog is shown and the GUI becomes unresponsive.
wasn't reproducible, I wouldn't have been able to figure out the problem (which happened in the past).
Even if the crash dialog would work, I'd prefer it to be a separate option instead of being set depending on the DEBUG option. My expectation when compiling ports with DEBUG is getting usable core dumps.
Fix: The attached patch removes the --enable-crash-dialog configure option which solves the problem for me.
Patch attached with submission follows:
How-To-Repeat: 1. Build the claws-mail port with "DEBUG" support
2. Crash claws-mail
3. Notice that there is no core dump to analyze
Over to maintainer (via the GNATS Auto Assign Tool)
Date: Thu Jan 24 15:51:35 2013
New Revision: 310935
Don't enable crash dialog when DEBUG=on - this prevents
coredump file creation.
Submitted by: Fabian Keil <firstname.lastname@example.org>
--- head/mail/claws-mail/Makefile Thu Jan 24 15:48:20 2013 (r310934)
+++ head/mail/claws-mail/Makefile Thu Jan 24 15:51:35 2013 (r310935)
@@ -151,7 +151,7 @@ CONFIGURE_ARGS+= --disable-pgpmime-plugi
-CONFIGURE_ARGS+= --enable-maintainer-mode --enable-crash-dialog
email@example.com mailing list
To unsubscribe, send any mail to "firstname.lastname@example.org"