Arm-linux-gnueabihf-gdb vs gdb-multiarch

I am trying to perform cross-platform remote debugging from my x86 computer to a remote ARM device. (ex: Beagle Bone Black)

I am using Ubuntu 14.04 and Eclipse CDT.

I installed the gcc-arm-linux-gnueabihf package , but the gdb debugger is not in this package. ( http://packages.ubuntu.com/precise/gcc-arm-linux-gnueabihf )

Therefore, I am wondering if I should use the Linaro toolchain (including arm-linux-gnueabihf-gdb ), or if I should install the gdb-multiarch package.

What is the difference between gdb-multiarch and arm-linux-gnueabihf-gdb? Is it better to use gdb-multiarch?

ssinfod

+6
source share
2 answers

I got a response from the linaro mailing list:

For Ubuntu hosts since April 12, gdb-multiarch has been used as a gdb client for debugging. Since the name indicates that it is a regular client for any architecture and is not limited to ARM.

Typically, all gdb clients are architecture independent, since the architecture part is handled by gdbserver itself. So, besides the name arm-linux-gnueabihf-gdb, I assume that it is the same as gdb-multiarch.

+6
source

I got another answer from the linaro mailing list:

The linar version of gdb will generally be more relevant than Ubuntu alone. For example, our latest version is 7.8, and it is only available in the utopian, not true, so if you plan to use the Ubuntu LTS release, it may be better to use the supplied Linaro gdb. Linaro gdb also contains fixes and improvements that are not in the upstream stable branch. Historically, Ubuntu has often chosen these changes too, but this may not always be the case.

gdb-multiarch obviously supports a number of architectures other than ARM, so if this is something that would be useful to you, then it might make sense to use this.

+1
source

Source: https://habr.com/ru/post/973379/


All Articles