Backtraces - Revision history

Iz0bbz: /* Backtraces in Fedora : Using ABRT */

2011-06-21T12:49:18Z

‎Backtraces in Fedora : Using ABRT

2010-12-02T11:35:53Z

2009-08-02T06:27:02Z

‎On Gentoo

2009-07-31T16:39:29Z

‎On Gentoo

2009-07-31T16:37:15Z

‎Compiling aMule on gentoo

2009-07-04T17:51:27Z

‎Introduction

2008-09-24T14:05:23Z

Corrected Spelling of Español in language selection

2008-08-18T22:29:53Z

Added another example

2008-08-12T09:18:37Z

Two new sections

2008-06-29T08:47:55Z

Removed Version Tag

@@ Line 142: / Line 142: @@
 ABRT can be used to provide useful amule backtraces on the following conditions:
-* you are running Fedora 14 or later
+* you are running Fedora 14 or newer
 * amule is installed from rpmfusion, or you have compiled yourself amule with debug information (see above), using Fedora wxGTK libraries
 You can find information on ABRT usage at the following link:
 * [https://fedorahosted.org/abrt/wiki/AbrtBasicFunctionality ABRT Basic functionality]
 == Links ==
 * [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]

@@ Line 135: / Line 135: @@
 Well, this is what I call a useful backtrace. It has both global and local symbols and line numbers. Now we can see the program state as it was at the time of the crash, and can possibly "easily" identify, what went wrong.
 == Links ==
 * [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]

@@ Line 45: / Line 45: @@
 You must follow [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo].
-In short, most gentoo users want to edit /etc/make.conf, add "-ggdb" into their CFLAGS and
+In short, most gentoo users want to edit ''/etc/make.conf'', add ''-ggdb'' into their CFLAGS and
   FEATURES="splitdebug"
 Those are needed by gdb in order to find the debug symbols.
 Emerge amule as usual with
   USE="debug" emerge amule
-If you don't use "USE="debug"", you will get a little bit less information from gdb, so it is better to use it.
+If you don't use ''USE="debug"'', you will get a little bit less information from gdb, so it is better to use it.
-After merging amule, you can safely remove -ggdb and splitdebug from /etc/make.conf.
+After merging amule, you can safely remove ''-ggdb'' and ''splitdebug'' from ''/etc/make.conf''.
 == Create a backtrace ==

@@ Line 51: / Line 51: @@
   USE="debug" emerge amule
 If you don't use "USE="debug"", you will get a little bit less information from gdb, so it is better to use it.
 == Create a backtrace ==

← Older revision		Revision as of 16:37, 31 July 2009
Line 41:		Line 41:

	If you are unable or unwilling to recompile, or are running a RPM version, proceed anyway, but be aware that backtraces from debugging enabled builds are much more useful to us.		If you are unable or unwilling to recompile, or are running a RPM version, proceed anyway, but be aware that backtraces from debugging enabled builds are much more useful to us.
		+
		+	=== On Gentoo ===
		+	You must follow [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo].
		+
		+	In short, most gentoo users want to edit /etc/make.conf, add "-ggdb" into their CFLAGS and
		+	FEATURES="splitdebug"
		+	Those are needed by gdb in order to find the debug symbols.
		+	Emerge amule as usual with
		+	USE="debug" emerge amule
		+	If you don't use "USE="debug"", you will get a little bit less information from gdb, so it is better to use it.

	== Create a backtrace ==		== Create a backtrace ==

@@ Line 7: / Line 7: @@
 Well, not hard to guess, this is about backtraces.
-Usually, it should not be necessary for the normal user to do this. However, we might have a bad day and release a somewhat buggy version or you are running [http://www.gnu.org/software/cvs CVS] which can also be unstable sometimes.
+Usually, it should not be necessary for the normal user to do this. However, we might have a bad day and release a somewhat buggy version or you are running [http://subversion.tigris.org SVN] which can also be unstable sometimes.
 This is where the backtraces come in: if [[aMule]] crashes, and you get an "OOPS - aMule crashed" and so on, we'd like to know. The backtrace [[aMule]] provides is not always very usefull as it contains little information, but, as usual, there's a better way: A *real* backtrace.

← Older revision		Revision as of 14:05, 24 September 2008
Line 1:		Line 1:
−	<center>[[Backtraces\|English]] \| [[Backtraces-es\|~~Spanish~~]]</center>	+	<center>
		+	[[Backtraces\|English]] \|
		+	[[Backtraces-es\|Español]]
		+	</center>

	== Introduction ==		== Introduction ==

@@ Line 107: / Line 107: @@
 This is an exmple of an unuseful backtrace. It doesn't show where the error happened and what went wrong. If your backtrace looks like this, it is pretty unuseful for us. This backtrace is either created from a binary without debug information (stripped), or ''gdb'' was unable to parse it (see above section).
   #0  0x000000000046fcab in CUpDownClient::ClearDownloadBlockRequests (this=0x45bf9e0) at BaseClient.cpp:1175
@@ Line 113: / Line 120: @@
   ...
-This is an exmple of a useful backtrace. See, how the question marks of the above example have been turned into real function names, argument values and source file reference. This is the kind of backtrace we can work with.
+Well, this is what I call a useful backtrace. It has both global and local symbols and line numbers. Now we can see the program state as it was at the time of the crash, and can possibly "easily" identify, what went wrong.
 == Links ==
 * [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]

← Older revision		Revision as of 08:47, 29 June 2008
Line 89:		Line 89:
	== Links ==		== Links ==
	* [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]		* [http://www.gentoo.org/proj/en/qa/backtraces.xml How to get meaningful backtraces in Gentoo]
−
−	~~== Version ==~~
−	~~Created by "Unknown User" on 28.04.04 at 23:21<br>~~
−	~~Updated by Vollstrecker on 22.01.08 at 12:06~~