touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

That seems fine to me. The main thing we need from gdb on the client
side is calculation of a stack trace address signature, we don't need
the capabilities of the full gdb (like decoding Python objects) for
that.

I think a good regression test is something like this:

 - Ensure that you only have gdb-minimal installed
 - Trigger a crash, with e. g. sh -c 'kill -SEGV $$'
 - wait for the apport window to pop up
 - look at the details
 - Ensure you see a StacktraceAddressSignature, which should look something like:

    StacktraceAddressSignature: /bin/dash:11:/lib/x86_64-linux-
gnu/libc-2.19.so+373e7:/bin/dash+cc67:[...]

** Changed in: apport (Ubuntu Trusty)
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1347565

Title:
  apport recommends gdb

Status in “apport” package in Ubuntu:
  New
Status in “apport” source package in Trusty:
  In Progress
Status in “apport” source package in Utopic:
  New

Bug description:
  apport-kde (and apport-gtk) recommends gdb | gdb-minimal

  This brings in gdb and with it libc6-dbg onto the images which are now
  oversized (looking at trusty 12.04.1 candidates today).

  I'd like to switch this so gdb-minimal is recommended first for
  apport-kde.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1347565/+subscriptions