[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Mandatory -dbg packages for libraries?



On Mon, 2007-04-23 at 10:37 +0200, Josselin Mouette wrote:
> Le dimanche 22 avril 2007 à 20:39 +0100, Neil Williams a écrit :
> > I'd like to see all library source packages having a minimum of 4
> > binary packages required by Policy: the SONAME, the -dev,  the -dbg and
> > a -doc package. (Libraries for perl or other non-compiled languages
> > would be exempt from -dbg packages but not -doc.)
> 
> I fully concur, and I think we need to go farther, by adding a debugging
> package to *all* architecture-dependent packages. Of course, this
> requires changes at the dak level, in the mirror scripts (not all
> mirrors will want their size to double) and in APT. This was in Sam's
> platform and I hope to see some efforts happen in this direction.
> 
> With the introduction of debreaper, I'd like to make automated bug
> reporting a reality for the majority of unstable users, but it will be
> useless if there is no solution to install the debugging symbols
> automatically.
<snip>

Installing debugging symbols for all binaries involved in a crash
seems... heavyweight.  I would expect the user to want to get on with
his or her work at this point.

Wouldn't it be better - in terms of response rate - to take a
"minidump" (along the lines of Windows error reporting or Mozilla's
Quality Feedback Agent) and do symbol lookup on some central server?

It might also be worth looking at MS's symbol server.  I don't know
whether that supports queries by address or whether it just serves up
whole debug databases, but it seems to work reasonably quickly.  (But
unsurprisingly it's providing quite sparse information about Windows
binaries.)

Ben.

-- 
Ben Hutchings
When you say `I wrote a program that crashed Windows', people just stare ...
and say `Hey, I got those with the system, *for free*'. - Linus Torvalds

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: