# Add a sticky that explains how to post a bug!

**URL:** <https://community.asterisk.org/t/add-a-sticky-that-explains-how-to-post-a-bug/13098>\
**Category:** Asterisk Support\
**Created:** [March 15, 2007, 6:43am UTC](https://community.asterisk.org/t/add-a-sticky-that-explains-how-to-post-a-bug/13098 "2007-03-15T06:43:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mats](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@Mats](https://community.asterisk.org/u/Mats)\
**Post date:** [March 15, 2007, 6:43am UTC](https://community.asterisk.org/t/add-a-sticky-that-explains-how-to-post-a-bug/13098/1 "2007-03-15T06:43:35Z")

</div>

Hi,  
Could the “Sticky: [FAQ] - Support and Troubleshooting - _READ BEFORE POSTING_” be changed to include debugging info like the one serge-v wrote:

[i]When posting console output, it is helpful to include verbose / debug information. Please always _attach_ any output, not post it inline.

1. Make sure your logger.conf has the following line:  
console =\> notice,warning,error,debug
2. restart Asterisk with the following command:  
‘asterisk -Tvvvvvdddddngc | tee /tmp/verbosedebug.txt’
3. core set debug 4  
core set verbose 4
4. Reproduce the problem
5. Trim startup information and attach verbosedebug.txt to the issue.[/i]

And I have also seen one that explains debugging steps in cases when asterisk crash and it’s god to include a core dump into the bug report.

/Mats

---

<div class="post-metadata">

**Author:** ![baconbuttie](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/baconbuttie/32/916_2.png) [@baconbuttie](https://community.asterisk.org/u/baconbuttie)\
**Post date:** [March 15, 2007, 7:32am UTC](https://community.asterisk.org/t/add-a-sticky-that-explains-how-to-post-a-bug/13098/2 "2007-03-15T07:32:21Z")

</div>

> [@Mats](#):
>
> 5) Trim startup information and attach verbosedebug.txt to the issue.

you mean for [bugs.digium.com/](http://bugs.digium.com/) right ? not here.