-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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 an option to leave an interactive gdb session on crash #32810
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32810/20994
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-32810/20995
|
A new Pull Request was created by @dan131riley (Dan Riley) for master. It involves the following packages: FWCore/Services @makortel, @smuzaffar, @cmsbuild, @Dr15Jones can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-6b43ca/12699/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR adds an option for the stack trace handler to attach to gdb and leave an interactive session, instead of printing a backtrace and detaching. This allows for interactive investigation of bugs (particularly threading bugs) that don't manifest when run under gdb.
PR validation:
Tested (via
kill -SIGBUS
) that the default behavior is still the same, but withthe bus error signal leaves the terminal at an interactive
(gdb)
prompt attached to cmsRun.