From 4449d2027bf7066f836eef0dddb42f8b18e613b0 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Wed, 7 Mar 2001 20:09:05 +0000 Subject: More about reporting bugs. svn path=/trunk/; revision=3219 --- fetchmail-FAQ.html | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index f6ade859..84b93f35 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 2001/02/23 08:28:11 $ +$Date: 2001/03/07 20:09:05 $

Frequently Asked Questions About Fetchmail

@@ -264,6 +264,11 @@ greeting line, so I can identify it in case of server problems. This transcript will not reveal your passwords, which are specially masked out precisely so the transcript can be passed around.

+If you upgraded your fetchmail and something broke, you should include +session transcripts with -v -v of both the working and failing +versions. Very often, the source of the problem can instantly +identified by looking at the differences in protocol transactions.

+ If the bug involves a core dump or hang, a gdb stack trace is good to have. (Bear in mind that you can attach gdb to a running but hung process by giving the process ID as a second argument.) You will need to @@ -2922,7 +2927,7 @@ switching to IMAP and using a short expunge interval.

Back to Fetchmail Home Page To Site Map -$Date: 2001/02/23 08:28:11 $ +$Date: 2001/03/07 20:09:05 $

Eric S. Raymond <esr@snark.thyrsus.com>
-- cgit v1.2.3