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

List:       kde-devel
Subject:    Re: Thoughts from a former KDE, currently Mozilla developer
From:       George Kiagiadakis <kiagiadakis.george () gmail ! com>
Date:       2010-12-07 21:36:02
Message-ID: AANLkTimdto=iG=5nXSBaj0hvUcRmGeBf=dQFGj7SpEHw () mail ! gmail ! com
[Download RAW message or body]

On Tue, Dec 7, 2010 at 11:14 PM, Thiago Macieira <thiago@kde.org> wrote:
> On Tuesday, 7 de December de 2010 21:53:57 Benoit Jacob wrote:
>> 2010/12/7 Thiago Macieira <thiago@kde.org>:
>> > How are you going to properly find the stack without debug symbols?
>> >
>> > Imagine one frame that didn't keep the frame pointer properly?
>>
>> If the stack is damaged, then indeed I can't do anything; but that's
>> not the case in a vast majority of crashes.
>
> Who said anything about damaged?
>
> The stack can be safe, but require debugging information to find where the
> previous frame pointer was saved in the frame.
>
> Anyway, we need to know which version and build of each and every library in
> each and every distribution shipping KDE.
>

That's the real issue. The server would need to hold all the debug
symbols from all the kde binaries of all the kde versions of all the
possible distributions (and variants of them; for example, 2 gentoo
users building with different USE flags may have two kde versions that
are binary incompatible with each other). This simply doesn't scale.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]