[openbeos] automated bug report (WAS: Re: Bug-reporting on Mail Daemon Replacement)

  • From: Kobi Lurie <k_lurie@xxxxxxxxxxxxxx>
  • To: openbeos@xxxxxxxxxxxxx
  • Date: Fri, 22 Feb 2002 14:40:00 +0200

how hard can it be for the talented programmers of obos to produce a debug 
daemon (syslog daemon while you're 
at it? ;)
only this debug daemon won't send u to a terminal but instead will print to a 
file default (changed via pref?)
sc and regs .
the file can be then neatly saved into a directory structure like
/boot/home/crasher-bugs/system/app_name (if ran from /boot/beos/* )
                         /app_name             (else)
maybe the system bugs can have a dialog asking the user if s/he wants to 
generate an automated email (which will be 
sent to a database) -- in case the software is release quality. (not some 
developer making tests)

maybe there's some way to unify certain debugs instead of checking each one out.
like by a function or file it failed on (maybe as an attribute?)
-- this, i'm not sure could be easily done, since the debugger is a seperate 
app.

this could really ease a dev's life.
(maintaining a database of bugs in a simple folder)


there is a similar concept but much simpler in win nt, with saving to a text 
file, can't remember the daemon's name.

any comments?? ideas?

22/02/2002 10:29:16, "Rob Tijssen" <rob.tijssen@xxxxxxx> wrote:

>Hello,
>
>It would be nice to have some kind of an "automatic" bug reporting tool (a
>la Windows XP ;-) wich would allow us to make a bugreport ourselved too.
>Advantage for you guys would be to have a "standard" bugreport form to work
>through.
>
>just my humble opinion (euro 0,02),
>
>Greetz,
>
>Rob
>
>




Other related posts:

  • » [openbeos] automated bug report (WAS: Re: Bug-reporting on Mail Daemon Replacement)