misc/176862: supply debug libs for KDE binary pkgs

Torsten Eichstädt torsten.eichstaedt at web.de
Mon Mar 11 19:50:02 UTC 2013

>Number:         176862
>Category:       misc
>Synopsis:       supply debug libs for KDE binary pkgs
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 11 19:50:00 UTC 2013
>Originator:     Torsten Eichstädt
>Release:        9.1-RELEASE (PCBSD-9.1-RELEASE)
FreeBSD paul-lifebook.local.lan 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Tue Jan 29 15:02:50 EST 2013     root at avenger:/usr/obj/pcbsd-build64/fbsd-source/src-patched/sys/GENERIC  amd64

(The release given above is not 100% exact, I think PC-BSD contains some pkgs from STABLE, e.g. KDE 4.9.5 not 4.8.x)

To the KDE-FreeBSD maintainers:

When a KDE app crashes, KDE has a nice mechanism to automagically send debug output to the KDE devs, I think it's named "Dr. Konqi".  This also has a button to automagically install missing debug libs -- or is the latter a Kubuntu patch?

IMHO it would be useful if FreeBSD had binary debug libs for KDE available, i.e. generally I use the normal libs, but when some app crashes, "Dr. Konqi" loads the appropiate debug lib(s) and I can send a qualified bug report to KDE.

Maybe it's possible via compiler switches that the normal libs contain only hooks to debug info, and the debug libs contains only the additional infos?

Then, the next thing is KDE from ports.  This could probably be adjusted, too.
I.e. in general, I don't want debug libs for my ports, but for KDE -- well, it's a very complex biest and we all would like to see it more stable, right?

Or is this a PC-BSD special, i.e. FreeBSD does it like I propose and PC-BSD maintains it's own patched tree?  Anyway, I'm considering to come "down" to plain FreeBSD next week or so.

Thanx in advance!
see above


More information about the freebsd-bugs mailing list