Bug reporting - Revision history

Marian at 09:36, 9 July 2013

2013-07-09T09:36:22Z

2013-02-13T09:49:05Z

‎What to check before reporting?

2013-02-13T08:46:14Z

‎What to include in the report

2013-02-13T08:41:00Z

‎What to check before reporting?

2013-02-13T08:39:10Z

‎Creating core files

2013-02-13T08:23:02Z

‎Where to report bugs?

2013-02-13T08:05:39Z

‎Creating core files

2013-02-13T08:05:22Z

‎Creating core files

2013-02-13T08:04:33Z

2013-02-12T16:35:40Z

‎Where to report bugs?

← Older revision		Revision as of 09:36, 9 July 2013
Line 70:		Line 70:
	* [[Debug Output]]		* [[Debug Output]]
	* [[Mail List]]		* [[Mail List]]
		+	* [[Debugging Yate Client on Windows]]

@@ Line 11: / Line 11: @@
 * Make sure you are running a clean build of Yate. Subtle problems may be caused by partial builds. If the compiler crashed at any point you should clean everything and start building from start.
 * Read the [[Modules|Documentation]] - especially the parts related to your problem.
-* Verify if any other equipment or software you use is [[Compatibility|compatible]] with Yate.
+* Verify if any other equipment or software you use is compatible with Yate.
 * Check the [http://yate.null.ro/mantis/ Bug tracker] for open bug reports of the problem. Please look at the closed and resolved bugs too - the problem may have been already fixed in a new release or in SVN.
 * Check the [http://yate.null.ro/archive/ List archive] if the problem wasn't reported before.

@@ Line 35: / Line 35: @@
 Crashes caused by memory corruptions leave useless core files (since the damage was caused earlier, typically by a different thread). If you see "''glibc detected ... memory corruption''" then please do not post such backtraces. The logs may provide some information about what went wrong.
-'''NOTE''' A backtrace is usefull only if it includes symbol information. You can compile the debug version of Yate, either by "make debug" or choosing the "Win32 Debug" configuration (in Windows).
+ '''NOTE''' A backtrace is usefull only if it includes symbol information. You can compile the debug version of Yate, either by "make debug" or choosing the "Win32
 == Where to report bugs?==

@@ Line 9: / Line 9: @@
 Before making a bug report you should check if the problem was known before. Someone may be working on it, it may have been fixed or there may be workarounds.
-* Make sure you are running a clean build of Yate, especially if using CVS. Subtle problems may be caused by partial builds. If the compiler crashed at any point you should clean everything and start building from start.
+* Make sure you are running a clean build of Yate. Subtle problems may be caused by partial builds. If the compiler crashed at any point you should clean everything and start building from start.
 * Read the [[Modules|Documentation]] - especially the parts related to your problem.
 * Verify if any other equipment or software you use is [[Compatibility|compatible]] with Yate.
-* Check the [http://yate.null.ro/mantis/ Bug tracker] for open bug reports of the problem. Please look at the closed and resolved bugs too - the problem may have been already fixed in a new release or in CVS.
+* Check the [http://yate.null.ro/mantis/ Bug tracker] for open bug reports of the problem. Please look at the closed and resolved bugs too - the problem may have been already fixed in a new release or in SVN.
 * Check the [http://yate.null.ro/archive/ List archive] if the problem wasn't reported before.
 * Ask our friend [http://www.google.com/ Google]

@@ Line 41: / Line 41: @@
 There are several places you can use to report bugs:
 * For small problems or just to quickly ask a question you can use IRC - the #yate channel on the Freenode network (irc.freenode.net)
-* More complex problems can be asked on the [[Mail list]] - the answer may be slower but more people may be able to answer.
+* More complex problems can be asked on the [[Mail List]] - the answer may be slower but more people may be able to answer.
 * Finally, there's the [http://yate.null.ro/mantis/ Bug tracker] where you can report a problem, add notes, logs and patches and track how the report was handled.

← Older revision		Revision as of 08:05, 13 February 2013
Line 63:		Line 63:
	* Make sure you set something like '''ulimit -c unlimited''' or start Yate with the -C command line option		* Make sure you set something like '''ulimit -c unlimited''' or start Yate with the -C command line option
	* Check if core size limits aren't restricted by the superuser, system policy or filesystem quota		* Check if core size limits aren't restricted by the superuser, system policy or filesystem quota
		+
		+
		+	'''See also'''
		+
		+	* [[Debug output]]

← Older revision		Revision as of 08:04, 13 February 2013
Line 1:		Line 1:
−	~~==General==~~	+
	Bugs or missing features are always possible in any software or other branches of engineering. We will try to fix the problems in Yate as soon as possible. Please note that our priorities may be different than yours...		Bugs or missing features are always possible in any software or other branches of engineering. We will try to fix the problems in Yate as soon as possible. Please note that our priorities may be different than yours...