[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Frequent crashes - backtrace posting?
From:       thorsten () staerk ! de
Date:       2006-09-16 19:30:40
Message-ID: 58206.84.168.112.248.1158435040.squirrel () mail ! staerk ! de
[Download RAW message or body]

AJ,

no, there is no macro recorder, but if you build your KDEPIM with
./configure --enable-debug=full && make && make install
you get a very valid backtrace that, in most cases, enables us to imagine
what went wrong during the program's usage.

Thorsten

> I wonder if there is a way to do something like a "Macro Recorder" so that
> in
> a debugging mode we can keep a copy of events that have been dispatched?
> Or
> perhaps a history of signals emitted?  This would make a slower system,
> but
> it could be only turned on while in a debugging mode.
>
> AJ
>
> On Friday 15 September 2006 4:31 am, David Faure wrote:
>> The problem with blindly posting backtraces though, is that they lack
>> instructions on how to trigger the crash... this makes them basically
>> useless since we can't test the fix to know if we have really fixed the
>> crash.
> _______________________________________________
> kde-pim mailing list
> kde-pim@kde.org
> https://mail.kde.org/mailman/listinfo/kde-pim
> kde-pim home page at http://pim.kde.org/
>

_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]