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.

Sign up for GitHub

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

Jump to bottom

Document how to get useful backtraces #13

Open
tintou opened this issue Nov 26, 2021 · 2 comments
Open

Document how to get useful backtraces #13

tintou opened this issue Nov 26, 2021 · 2 comments

Comments

@tintou
Copy link
Member

tintou commented Nov 26, 2021

Bug reports would be much better with proper crash logs, it would also probably help the 3rd party developers to have an easy way to get backtraces.

Here is an example of the steps:
elementary/wingpanel#416 (comment)
@danirabbit
Copy link
Member

We have bt and logs guides on the contributor docs: https://docs.elementary.io/contributor-guide/feedback/reporting-issues/inspecting-crashes and https://docs.elementary.io/contributor-guide/feedback/reporting-issues/debug-logs

It would probably be better to update or revise those pages

@danirabbit danirabbit transferred this issue from elementary/docs Dec 2, 2021
@marbetschar
Copy link
Member

marbetschar commented Jan 23, 2022 •
edited
Loading

I documented the debugging steps as well on my website. Feel free to copy & paste as you see fit:
https://www.marco.betschart.name/areas/elementary-os/debug-vala-or-c-app

danirabbit added a commit that referenced this issue Jul 11, 2022
@danirabbit @gitbook-bot
GitBook: [#13] No subject
1dcd106
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@marbetschar @tintou @danirabbit