Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for using a gdb-sandbox to crash-digger #198

Closed
wants to merge 2 commits into from

Conversation

murraybd
Copy link
Contributor

@murraybd murraybd commented Jul 8, 2023

I'm working on moving the service which retraces apport crashes in Launchpad to a different server and noticed that while the existing service uses crash-digger it does not take advantage of the gdb sandbox option which I added to apport some time ago. I've added an option to crash-digger, --gdb-sandbox, which is then is then passed through as argument to apport-retrace.

@codecov
Copy link

codecov bot commented Jul 8, 2023

Codecov Report

Merging #198 (aeff48e) into main (d5f1f43) will decrease coverage by 9.91%.
The diff coverage is 75.00%.

@@            Coverage Diff             @@
##             main     #198      +/-   ##
==========================================
- Coverage   82.66%   72.76%   -9.91%     
==========================================
  Files          91       89       -2     
  Lines       18546    17824     -722     
==========================================
- Hits        15331    12969    -2362     
- Misses       3215     4855    +1640     
Impacted Files Coverage Δ
bin/crash-digger 81.29% <75.00%> (-0.17%) ⬇️

... and 18 files with indirect coverage changes

@murraybd
Copy link
Contributor Author

murraybd commented Jul 8, 2023

I've tested the --gdb-sandbox option on the server too.

@murraybd murraybd requested a review from bdrung July 8, 2023 00:18
@bdrung
Copy link
Collaborator

bdrung commented Jul 11, 2023

Can you add a test case for --gdb-sandbox to test/integration/test_crash_digger.py please?

@bdrung
Copy link
Collaborator

bdrung commented Jul 19, 2023

I have taken your merge request and added the needed test case in #205.

@bdrung bdrung closed this Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants