How to proceed with MiniDebugInfo

Alexander Larsson alexl at redhat.com
Thu May 24 09:24:38 UTC 2012


On Thu, 2012-05-24 at 11:17 +0200, Jiri Moskovcak wrote:
> On 05/24/2012 11:07 AM, Alexander Larsson wrote:
> > On Thu, 2012-05-24 at 11:22 +0300, Yanko Kaneti wrote:
> >
> > The duplication of effort less so IMHO, as different people are doing
> > the work. If we don't do minidebug I will not be spending any resources
> > on the ABRT server anyway. So, not doing minidebug will not affect ABRT
> > positively, and doing it will not affect it negatively (in fact, it
> > might have a slight positive effect as it can use the low quality info
> > when offline). But still, as this is mainly a resource/project
> > management disagreement it might make sense to have Fesco look at it
> > too.
> 
> In fact it will affect ABRT positively - the calltrace with function 
> names is a pretty good for duplicate checking, so ABRT will be able to 
> find the dupes in already filled bugzilla tickets without requiring the 
> full debuginfo.

Well, theoretically it could do that by retracing the backtrace on the
server. It seems much simpler and more efficient to just do that locally
though, but this is partly where the disagreement is.




More information about the devel mailing list