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:
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 ssSignature, which should look something like:
- 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 StacktraceAddre
StacktraceA ddressSignature : /bin/dash: 11:/lib/ x86_64- linux-gnu/ libc-2. 19.so+373e7: /bin/dash+ cc67:[. ..]