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

[dev.icinga.com #8575] Include GDB backtrace in crash reports #2696

Closed
icinga-migration opened this issue Mar 3, 2015 · 1 comment
Closed
Labels
enhancement New feature or request
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/8575

Created by gbeutner on 2015-03-03 12:53:49 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2015-03-03 12:55:04 +00:00)
Target Version: 2.3.0
Last Update: 2015-03-03 12:55:04 +00:00 (in Redmine)

Backport?: No
Include in Changelog: 1

Changesets

2015-03-03 12:53:11 +00:00 by (unknown) 3615716

Include GDB backtrace in crash reports

fixes #8575
@icinga-migration
Copy link
Author

Updated by Anonymous on 2015-03-03 12:55:04 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 3615716.

@icinga-migration icinga-migration added enhancement New feature or request libbase labels Jan 17, 2017
@icinga-migration icinga-migration added this to the 2.3.0 milestone Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant