disabling crashhandler in trunk.

[Mark Kretschmann]

On Saturday 10 March 2007 21:29, Dan Meltzer wrote:
> During porting I changed crashhandler to dump output to stdout instead
> of  trying to invoke a mail client as a temporary thing until things
> got closer to working.  After a while, I'm starting to not like this
> that much.  For some reason the crashhandler is a whole lot more
> resource intensive in trunk, and takes a lot longer to run--A lot of
> things cause crashes as well.  Due to this, a lot of time can be spent
> waiting for amarok to finish crashing in order to test whatever it is
> one is working on.  I'd like to propose that we disable the
> crashhandler completely in trunk for now.
>
> 1) running gdb against amarokapp manually gives more control anyways
> if one is working against a crash
> 2) We have no real user base that would be able to benefit from having
> it dumped automagically.
> 3) It allows for the act of running gdb against amarok to be
> optional--isntead of a resource heavy ordeal that happens a lot right

Yeah, I've been annoyed by the crashhandler too. I think dumping the backtrace 
to stdout is a great idea! No need to fire up gdb or mess with core files. 

-- 
Mark