Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Help in setting up remote debugging on ARM Linux

Hi Marc,

> I'm probably not understanding properly what you're having trouble with but doesn't the automatic remote launch have two places to specify binary? One at the top of the main tab for the host and one lower down for the remote. The text for the remote one says "Remote absolute file path for C/C++ application"
> 
> BR,
> Marc

I wish it could be so simple.

Like I said, the name of the binary passed to cross-gdb and to gdbserver is currently can be specified in one place only, in "C/C++ Application". The "Remote absolute file path for C/C++ application" specifies where on the target this application will be located. If you put another name here (any name), your application binary (as entered in "C/C++ Application") will be just renamed to this name. This is not I want to achieve.

Anyway, thanks for the feedback.

Regards,
Sergei

On Wed, 2 Mar 2016 19:26:37 +0300
Sergei Poselenov <sposelenov@xxxxxxxxxxx> wrote:

> Hello,
> 
> (Initially posted here https://www.eclipse.org/forums/index.php/t/1075245/, but received no replies. Sorry if duplicated.)
> 
> I'm trying to set up remote debugging on my Cortex-M board running Linux.
> I was able to get gdbserver and ssh/sftp to the target, and configured the Automatic Remote Debugging Launcher for my target. Everything seems to work fine, however I can't get over one major obstacle.
> 
> In short, I need to specify one type of binary to be run under gdbserver on the target, and another type for the cross-gdb on the host.
> 
> Cross-compiler normally creates two binaries - the binary in the Binary Flat (BFLT) format and the ARM ELF binary. The BFLT binary (eg "hello") is the one which is ran on the target, and the ELF binary ("hello.gdb", with symbolic information) is the one which is used by the cross-debugger on the host to establish a debugging session with the target, eg:
> <target>:
>  gdbserver :1234 hello
> <host>:
>  arm-uclinuxeabi-gdb hello.gdb
>  gdb> target remote <target-ip>:1234
> ...
> 
> That is, I racked my brain on how to specify the Automatic Launcher to pass "hello" as the binary which need to be SFTP-ed to the target and started under gdbserver, and, at the same time, how to pass "hello.gdb" to arm-uclinuxeabi-gdb as the argument. Looks like the Automatic Launcher only allows to specify one of them in the "Debug Configuration" Main tab?
> 
> Using the Manual Launcher (and starting gdbserver on the target manually) works just fine.
> 
> I'm using Mars.1/Linux.
> 
> Any ideas? Thanks in advance.
> 
> Regards,
> Sergei


Back to the top