Remote debugging with gdb error - Remote 'g' packet reply is too long:

[Andrew Gillan]

I am setting up remote debugging via gdbserver with Eclipse on my Beaglebone A6.  I am getting the following error message:

Error in final launch sequence

Failed to execute MI command:

-target-select remote 192.168.0.15:2345

Error message from debugger back end:

Remote 'g' packet reply is too long: 

On the Beagleboard I grabbed gdbserver using:

> opkg install gdbserver

On my dev machine running Ubuntu 12.10 I pulled the multi architecture gdb using:

> apt-get install gdb-multiarch

I've set remote debugging up successfully before on my Beagleboard C3 but I used gdb from a toolchain I got off narcissus.

I appears there is a difference between the arm-linux-gnueabi and arm-angstrom-linux-gnueabi toolchains.  Can anyone enlighten me on the differences?

In the meantime I will see if using gdb from the angstrom generated toolchain solves my problem.

Thanks,

Andrew

[Vesa Jääskeläinen]

On 3.11.2012 1:51, Andrew Gillan wrote:
> I am setting up remote debugging via gdbserver with Eclipse on my
> Beaglebone A6. I am getting the following error message:
>
> Error in final launch sequence
> Failed to execute MI command:

> -target-select remote 192.168.0.15:2345 <http://192.168.0.15:2345>

> Error message from debugger back end:
> Remote 'g' packet reply is too long:
>
> On the Beagleboard I grabbed gdbserver using:
>> opkg install gdbserver
>
> On my dev machine running Ubuntu 12.10 I pulled the multi architecture
> gdb using:
>> apt-get install gdb-multiarch
>
> I've set remote debugging up successfully before on my Beagleboard C3
> but I used gdb from a toolchain I got off narcissus.
>
> I appears there is a difference between the arm-linux-gnueabi and
> arm-angstrom-linux-gnueabi toolchains. Can anyone enlighten me on the
> differences?
>
> In the meantime I will see if using gdb from the angstrom generated
> toolchain solves my problem.

Hi Andrew,

Easiest is to take gdb from �ngstr�m to both host (gdb-cross) and to
target (gdbserver):

http://elinux.org/GDB#Openembedded

I think the point in doing it this way is that they both are from same
version of gdb and both has been compiled with same compiling flags. GDB
seems to be a bit picky on those.

Thanks,
Vesa J��skel�inen

[tvv...@gmail.com]

Hi, Andrew Gillan!

you solved the problem?

суббота, 3 ноября 2012 г., 3:51:12 UTC+4 пользователь Andrew Gillan написал: