retitle 570085 Dependencies on debugging package not tight enough thanks Hi Mike,
On Tuesday 16 February 2010 18.18:28 Mike Hommey wrote:
> Once you remove the libimgicon.so file, what happens if you run
> iceweasel, attach gdb to it, and get a backtrace at a random time ? Do
> you get symbols ?
Aaah...
There's my problem:
++++
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Description
+++-=======================================================-===========================-============================================
ii iceweasel 3.5.6-2
Web browser based on Firefox
ii iceweasel-dbg 3.5.6-2
debugging symbols for iceweasel
ii xulrunner-1.9.1 1.9.1.6-2
XUL + XPCOM application runner
ii xulrunner-1.9.1-dbg 1.9.1.6-1
Development files for the Gecko engine libra
++++
One update later I get a sensible[1] backtrace.
The problem was that aptitude decided that instead of installing the
xulrunner-dbg to match the xulrunner, it would just add python-xpcom
to satisfy the dependencies.
I guess the solution is to add a
Conflicts: xulrunner-1.9.1 (!= ${binary:Version}), python-xpcom (!=
${binary:Version})
to the debugging package to catch this.
cheers
-- vbi
[1] As far as it goes. Still looks insane to me. But then I guess this
time that's only because I'm no good C++ programmer ;-)
--
featured link: http://www.pool.ntp.org
signature.asc
Description: This is a digitally signed message part.
