xwem-devel
[Top] [All Lists]

Re: [XWEM Bug] Example Bug Report

From: Zajcev Evgeny <lg@xxxxxxxx>
Subject: Re: [XWEM Bug] Example Bug Report
Date: Sun, 05 Dec 2004 13:10:25 +0300
Organization: xwem.org
User-agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Security Through Obscurity, berkeley-unix)
Steve Youngs <steve@xxxxxxxx> writes:

> Greetings Earthlings:
>
> Here is what the XWEM bug reports will look like.  Yes, it's long, but
> it's better to have too much information than not enough.
>
> The only thing this example doesn't show is a list of installed DSO's,
> I was running 21.4 at the time and didn't have any DSO's to install.
>
> All the user has to do is `M-x xwem-report-bug RET y some subject RET'
> and then type in a description of the problem and send.  It will only
> report the values of variables that have been changed from the
> default.  So if something isn't listed, it is at the default value (in
> theory).
>
> Backtrace, gdb, xwem-debug, and xwem-messages buffers are
> automatically included if they exist.
>
> I'm temporarily setting `print-level' to 5 so the bug reports aren't
> 78 terabytes long.
>
> This is in CVS now.  Apart from the new file, all existing files that
> have defcustom's have been touched as well.  I had to set them up so
> the bug-reporter would only scan for user variables.
>
> http://www.xwem.org/packages/ has up to the second XEmacs packages
> which includes this stuff.
>

SUPER JOB!!!  It is easy to figure out(using reported info) that you
dont have problems at bug report time :)

-- 
XWEM - Making GNU/Emacs users everywhere question their choice.

<Prev in Thread] Current Thread [Next in Thread>