GDB - Revision history

JulienB: /* Links */

2016-06-03T10:40:50Z

‎Links

2011-11-14T09:31:04Z

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

2011-11-07T14:16:30Z

‎Troubleshots

2011-07-05T09:51:58Z

2011-06-17T08:25:18Z

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

2010-10-14T08:12:03Z

add libthread_db.so hint

2010-08-01T19:16:09Z

2009-10-27T16:50:32Z

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

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

@@ Line 111: / Line 111: @@
 ==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.linux-france.org/article/memo/node119.html Déboguage avec gdb]

@@ Line 64: / Line 64: @@
   $ make
 </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:

@@ Line 80: / Line 80: @@
 ==Troubleshots==
-If you see that kind of error message when using gdb:
+===pthread debugging===
 <pre class="apf">
 dlopen failed on 'libthread_db.so.1' - File not found
@@ Line 97: / Line 98: @@
      ...
 </pre>
 Save your uClibc config and make it standard for next build:
 <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>
-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">
-$ rm -rf buildroot/toolchain_build_armv5te
+$ rm -rf buildroot/output
-$ rm -rf buildroot/build_armv5te
-$ rm -rf buildroot/project_build_armv5te
 $ make
 </pre>

@@ 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:
 <pre class="host">
-$ make uclic-menuconfig
+$ make uclibc-menuconfig
 </pre>
 <pre class="config">

@@ Line 27: / Line 27: @@
 <pre class="host">
   []$ 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
 </pre>

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

← Older revision		Revision as of 19: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]]

@@ Line 49: / Line 49: @@
 </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)==

@@ Line 45: / Line 45: @@
 <pre class="apf">
   # ps
-...
+... get process PID
-# gdbserver 192.168.0.2:2345 --attach PID
+ # gdbserver 192.168.0.2:2345 --attach PID
 </pre>

@@ Line 17: / Line 17: @@
 </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:
 <pre class="apf">
@@ Line 42: / Line 42: @@
 </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
 ==Debugging directly on your APF (may require more memory)==