[RFC] automatically create bug report with traceback etc.?

[Martin Pool]

On 21 Oct 2006, Alexander Belchenko <bialix at ukr.net> wrote:
> Hi!
> 
> As far as bzr wide among Windows users there is grow count of strange
> bug reports, and almost every time I'd like to see to actual traceback,
> because bzr hide this sort of info in most cases (when there is
> something related to the filesystem: file not found etc.).
> 
> I thinking about some plugin (or [hided] built-in command) that extract
> info from .bzr.log about last failure and format it to the bug report
> with all required info. After operation bzr either save this file to
> current directory or ask to user where he/she wants to save it. User
> could send this generated bug report to the list.
> 
> I think about this feature because there is 2 location where .bzr.log
> could exist on Windows. And because make this automatically will be very
> easy for our users.

Most errors that indicate a bug should now be producing a traceback to
stderr.  However, there may be some errors that are incorrectly marked
as user_error.  Are the bugs you're talking about here ones that produce
a traceback to stderr?

A few other things we could do:

 - save the traceback to a file as long as stderr, so it's easier to
   attach to a mail

 - perhaps save this traceback for all errors even if we think they're
   user errors

I'm not particularly tied to .bzr.log containing all errors.

-- 
Martin