| Summary: | ASTERISK-04911: for backtraces | ||
| Reporter: | Clod Patry (junky) | Labels: | |
| Date Opened: | 2005-08-26 18:01:23 | Date Closed: | 2008-01-15 15:46:25.000-0600 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Documentation |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) README.backtrace ( 1) README-1.backtrace | |
| Description: | I created a small README how to provide backtraces, cause i saw a lot of people uploading core files or asked how to provide backtraces or what are backtraces. Some others have no idea how to provide crucial informations, required by all asterisk developpers. | ||
| Comments: | By: Kevin P. Fleming (kpfleming) 2005-08-26 18:52:45 This will need some language cleaning, but it's a very nice start :-) Can you also add some text about ensuring that Asterisk is built without optimization ('make dont-optimize') so that backtraces reflect all the information needed? By: Clod Patry (junky) 2005-08-26 21:53:24 That version should fixes a lot of language cleaning, if i wanna say a great thanks to blitzrage for that review. That one sounds better? I'll provide infos, later, without optimization. By: Kevin P. Fleming (kpfleming) 2005-08-30 23:27:54 Yes, that's much better, nice work :-) Committed to CVS HEAD. By: Digium Subversion (svnbot) 2008-01-15 15:46:25.000-0600 Repository: asterisk Revision: 6467 A trunk/doc/README.backtrace ------------------------------------------------------------------------ r6467 | kpfleming | 2008-01-15 15:46:24 -0600 (Tue, 15 Jan 2008) | 2 lines add doc on how to create backtraces for debugging (issue ASTERISK-4911) ------------------------------------------------------------------------ http://svn.digium.com/view/asterisk?view=rev&revision=6467 | ||