describes how to get a stacktrace for a crasher. If you can reproduce the crasher of an existing bug and it is missing a stacktrace, it is of great help to add the stacktrace to the bug.
Deleted "Easyhack" from summary.
This article describes step by step how to get a backtrace in WinDbg (Windows debugger tool).
Report a crash in LibreOffice like a pro screencast
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility.
see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
*** This bug has been marked as a duplicate of bug 46892 ***
This link no longer leads to stacktrace instructions:
Where can the instructions be found?
how to get a backtrace on Linux, Windows or Mac is documented on this page:
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyBeginner TopicQA)
Remove LibreOffice Dev List from CC on EasyHacks
(curtailing excessive email to list)