GDB - Revision history

JulienB: /* Links */

2016-06-03T10:40:50Z

Links

← Older revision		Revision as of 12:40, 3 June 2016
Line 111:		Line 111:

	==Links==		==Links==
	* [~~http~~://~~sources~~.~~redhat~~.~~com~~/gdb/current/onlinedocs/~~gdb_5~~.html Debugging with GDB manual]		* [https://www.sourceware.org/gdb/current/onlinedocs/gdb/index.html Debugging with GDB manual]
	* http://www.kegel.com/linux/gdbserver.html		* http://www.kegel.com/linux/gdbserver.html
	* [http://www.linux-france.org/article/memo/node119.html Déboguage avec gdb]		* [http://www.linux-france.org/article/memo/node119.html Déboguage avec gdb]

2011-11-14T09:31:04Z

Debugging directly on your APF (may require more memory)

← Older revision		Revision as of 11:31, 14 November 2011
Line 64:		Line 64:
	$ make		$ make
	</pre>		</pre>
	Then you can either reflash your rootfs, or copy ''$ARMADEUS_ROOTFS_DIR/bin/gdb'' to your board, to a SD or to a NFS export.		Then you can either reflash your rootfs, or copy ''$ARMADEUS_ROOTFS_DIR/usr/bin/gdb'' to your board, to a SD or to a NFS export.

	* After installation, launch gdb on your APF:		* After installation, launch gdb on your APF:

2011-11-07T14:16:30Z

Troubleshots

← Older revision		Revision as of 16:16, 7 November 2011
Line 80:		Line 80:

	==Troubleshots==		==Troubleshots==
	If you see that kind of error message when using gdb:		===pthread debugging===
			* If you see that kind of error message when using gdb:
	<pre class="apf">		<pre class="apf">
	dlopen failed on 'libthread_db.so.1' - File not found		dlopen failed on 'libthread_db.so.1' - File not found
Line 97:		Line 98:
	...		...
	</pre>		</pre>
	Save your uClibc config and make it standard for next build:
			* Save your uClibc config and make it standard for next build:
	<pre class="host">		<pre class="host">
	$ cp buildroot/~~toolchain_build_armv5te~~/uClibc-0.9.29/.config buildroot/target/device/armadeus/~~apf27~~/uClibc.config.arm		$ cp buildroot/output/toolchain/uClibc-0.9.30.3/.config buildroot/target/device/armadeus/apfXX/uClibc.config.arm
	</pre>		</pre>

	Then rebuild all the toolchain ('''this will erase your local modifications !!''')		* Then rebuild all the toolchain ('''this will erase your local modifications !!''')
	<pre class="host">		<pre class="host">
	$ rm -rf buildroot/~~toolchain_build_armv5te~~		$ rm -rf buildroot/output
	~~$ rm -rf buildroot/build_armv5te~~
	~~$ rm -rf buildroot/project_build_armv5te~~
	$ make		$ make
	</pre>		</pre>

2011-07-05T09:51:58Z

← Older revision		Revision as of 11:51, 5 July 2011
Line 88:		Line 88:
	''libthread_db.so'' (db == debug) is a library that is needed when you want to debug programs using pthread. You will have to reconfigure the uClibc to get it build:		''libthread_db.so'' (db == debug) is a library that is needed when you want to debug programs using pthread. You will have to reconfigure the uClibc to get it build:
	<pre class="host">		<pre class="host">
	$ make ~~uclic~~-menuconfig		$ make uclibc-menuconfig
	</pre>		</pre>
	<pre class="config">		<pre class="config">

2011-06-17T08:25:18Z

Debugging a program running on your APF remotely from your Host (through Ethernet)

← Older revision		Revision as of 10:25, 17 June 2011
Line 27:		Line 27:
	<pre class="host">		<pre class="host">
	[]$ arm-linux-gdb program		[]$ arm-linux-gdb program
	(gdb) set solib-absolute-prefix ./buildroot/~~build_armv4t~~/staging_dir/		(gdb) set solib-absolute-prefix ./buildroot/output/build/staging_dir/
	(gdb) target remote 192.168.0.10:2345		(gdb) target remote 192.168.0.10:2345
	</pre>		</pre>

2010-10-14T08:12:03Z

add libthread_db.so hint

@@ Line 77: / Line 77: @@
 <pre class="apf">
   # gdb your_prog -c your_core_file
 </pre>

2010-08-01T19:16:09Z

← Older revision		Revision as of 21:16, 1 August 2010
Line 86:		Line 86:
	* [[KGDB\|KGDB (for kernel debugging)]]		* [[KGDB\|KGDB (for kernel debugging)]]

	~~{{LanguageBar\|GDB\|GDB\|GDB}}~~

	[[Category:Debug]]		[[Category:Debug]]

2009-10-27T16:50:32Z

Debugging a program running on your APF remotely from your Host (through Ethernet)

← Older revision		Revision as of 18:50, 27 October 2009
Line 49:		Line 49:
	</pre>		</pre>

	{{Note\|Core dump analysis doesn't seem to work in this use case (= on the Host with arm-linux-gdb) !!}}		{{Note\|Core dump analysis doesn't seem to work in this use case (ie on the Host with arm-linux-gdb) !!}}

	==Debugging directly on your APF (may require more memory)==		==Debugging directly on your APF (may require more memory)==

2009-10-27T16:49:30Z

Debugging a program running on your APF remotely from your Host (through Ethernet)

2009-10-27T16:49:07Z

Debugging a program running on your APF, from your Host, through Ethernet

← Older revision		Revision as of 18:49, 27 October 2009
Line 17:		Line 17:
	</pre>		</pre>

	==Debugging a program running on your APF, from your Host, through Ethernet==		==Debugging a program running on your APF remotely from your Host (through Ethernet)==
	* On the target launch your program like that:		* On the target launch your program like that:
	<pre class="apf">		<pre class="apf">
Line 42:		Line 42:
	</pre>		</pre>

	{{Note\|Core dump analysis doesn't seem to work in this use case !!}}		* If the program is already running, gdbserver can attach itself to the process, if you give him its PID
			<pre class="apf">
			# ps
			...
			# gdbserver 192.168.0.2:2345 --attach PID
			</pre>

			{{Note\|Core dump analysis doesn't seem to work in this use case (= on the Host with arm-linux-gdb) !!}}

	==Debugging directly on your APF (may require more memory)==		==Debugging directly on your APF (may require more memory)==