GDB - Revision history

Emistry at 16:50, 10 April 2015

2015-04-10T16:50:17Z

Haru: /* Using gdb with Hercules */ Additional info about debug builds

2015-02-25T18:14:46Z

‎Using gdb with Hercules: Additional info about debug builds

Dastgirpojee: /* Using gdb with Hercules */

2013-12-06T10:28:36Z

‎Using gdb with Hercules

Dastgirpojee: /* Using gdb with Hercules */

2013-12-06T10:27:36Z

‎Using gdb with Hercules

Dastgirpojee at 17:45, 3 October 2013

2013-10-03T17:45:08Z

Xgear: Removing _sql from binary names as they are no longer used.

2013-06-23T18:59:15Z

Removing _sql from binary names as they are no longer used.

Dastgirpojee: Created page with "GDB stands for GNU Debugger. It is a program for *nix related systems that allows you to view stacktrace and coredumps of your servers if it crashes. = Getting GDB = Typicall..."

2013-06-05T13:46:12Z

Created page with "GDB stands for GNU Debugger. It is a program for *nix related systems that allows you to view stacktrace and coredumps of your servers if it crashes. = Getting GDB = Typicall..."

New page

GDB stands for GNU Debugger. It is a program for *nix related systems that allows you to view stacktrace and coredumps of your servers if it crashes.

= Getting GDB =
Typically GDB comes installed on most *nix distro's. It comes installed on FreeBSD 7.1-RELEASE or newer if the ports collection is installed. Typically, it will be located in /usr/bin/gdb, but if it is not, you can either compile it from source or install it using your package manager for your distribution.

== Debian Based (apt-get, aptitude or synaptic) ==
On Debian based systems, you can use apt-get or aptitude, or the synaptic package manager to install gdb. If you prefer the terminal, you can issue ONE of the following to install gdb:

[sudo] aptitude install gdb
[sudo] apt-get install gdb

If you have access to gdm and the synaptic package manager, you can simply search for 'gdb' and mark for complete installation.

== YUM based (Redhat/CentOS) ==
On YUM based systems, you can simply issue the following to install gdb via RPM packages:

yum install gdb

== *BSD based ==
Typically GDM will come with an install of FreeBSD, but if it's not, it is best to make it from source, skip ahead.

== Compiling from source ==
Use your favourite download manager (wget, etc) to get the .tar.gz of the latest stable version of gdb from gdb's website. (http://www.gnu.org/software/gdb/)

Extract the .tar.gz using the following command:

tar -zxf gdb-x.xx.tar.gz

You need a GCC compatible compiler, so if you don't have one, get one now. there is a 99% chance that your distribution comes with a gcc compiler.

./configure && make && make install

Should install it for use. If you're on a *BSD based system, you may have to issue the following command to be able to use it.

% rehash

= Using gdb with eAthena =

Go to Your Hercules Folder and type the following command

ulimit -u unlimited

Restart the server then,
Find out which program(map/char/login server) crashed and it's core file (should be named the same as the server file with an additional ".core" extension).. then on the console, type:

gdb xxx-server_sql xxx-server_sql.core

You should get some limited output of the problem, or if the servers do not have a trace, you will get the following error:

No stack.

If it says Dump file was not found, then type the following command(The file is saved with other name)
gdb xxx-server_sql core

If a valid dump was found, you should get a prompt

gdb>

At that prompt, type:

gdb> bt full

And that will give you a full output of the problem area and a line number in which you should look for the crash. This just told you where the crash is located and what line you should look at to fix it. If you feel that is an eAthena development problem, feel free to submit a bug with that full report and one of the core developers can look into it.

= See Also =
* [http://www.gnu.org/software/gdb/download/ Download page for GDB]

@@ Line 73: / Line 73: @@
   make clean
   make sql
 = See Also =
 * [http://www.gnu.org/software/gdb/download/ Download page for GDB]
 [[Category:Debugging]]

@@ Line 42: / Line 42: @@
 Restart the server then,
-Find out which program(map/char/login server) crashed and it's core file (should be named the same as the server file with an additional ".core" extension).. then on the console, type:
+Find out which program(map/char/login server) crashed and its core file (should be named the same as the server file with an additional ".core" extension).. then on the console, type:
   gdb xxx-server xxx-server.core
@@ Line 67: / Line 67: @@
 And that will give you a full output of the problem area and a line number in which you should look for the crash. This just told you where the crash is located and what line you should look at to fix it. If you feel that is an Hercules development problem, feel free to submit a bug with that full report and one of the core developers can look into it.
 = See Also =
 * [http://www.gnu.org/software/gdb/download/ Download page for GDB]
 [[Category:Debugging]]

@@ Line 43: / Line 43: @@
 Restart the server then,
 Find out which program(map/char/login server) crashed and it's core file (should be named the same as the server file with an additional ".core" extension).. then on the console, type:
   gdb xxx-server xxx-server.core
@@ Line 51: / Line 52: @@
 If it says Dump file was not found, then type the following command(The file is saved with other name)
   gdb xxx-server core

← Older revision		Revision as of 17:45, 3 October 2013
Line 65:		Line 65:
	= See Also =		= See Also =
	* [http://www.gnu.org/software/gdb/download/ Download page for GDB]		* [http://www.gnu.org/software/gdb/download/ Download page for GDB]
		+	[[Category:Debugging]]

@@ Line 35: / Line 35: @@
   % rehash
-= Using gdb with eAthena =
+= Using gdb with Hercules =
 Go to Your Hercules Folder and type the following command
@@ Line 44: / Line 44: @@
 Find out which program(map/char/login server) crashed and it's core file (should be named the same as the server file with an additional ".core" extension).. then on the console, type:
-  gdb xxx-server_sql xxx-server_sql.core
+  gdb xxx-server xxx-server.core
 You should get some limited output of the problem, or if the servers do not have a trace, you will get the following error:
@@ Line 51: / Line 51: @@
 If it says Dump file was not found, then type the following command(The file is saved with other name)
-  gdb xxx-server_sql core
+  gdb xxx-server core
 If a valid dump was found, you should get a prompt
@@ Line 61: / Line 61: @@
   gdb> bt full
-And that will give you a full output of the problem area and a line number in which you should look for the crash. This just told you where the crash is located and what line you should look at to fix it. If you feel that is an eAthena development problem, feel free to submit a bug with that full report and one of the core developers can look into it.
+And that will give you a full output of the problem area and a line number in which you should look for the crash. This just told you where the crash is located and what line you should look at to fix it. If you feel that is an Hercules development problem, feel free to submit a bug with that full report and one of the core developers can look into it.
 = See Also =
 * [http://www.gnu.org/software/gdb/download/ Download page for GDB]