From: "Bahadir Balban" <bahadir.balban@gmail.com>
To: "Rakesh Kumar" <hkrakeshkumar@hotmail.com>
Cc: gdb@sourceware.org
Subject: Re: How to perform remote debugging using GDB for ARM processors
Date: Wed, 14 Feb 2007 15:32:00 -0000 [thread overview]
Message-ID: <7ac1e90c0702140704w6376607dt247f1dafca230b05@mail.gmail.com> (raw)
In-Reply-To: <BAY137-F81192800963AA0D0A38B9AA970@phx.gbl>
On 2/14/07, Rakesh Kumar <hkrakeshkumar@hotmail.com> wrote:
> Hi,
>
> I want to know how to go about the process of remote debugging using GDB for
> applications running/resident on ARM Processors.
>
> Regards,
> Rakesh Kumar H.K.
>
You need software on the target that supports the gdb stubs. Depending
on the connection setup, you should do something like:
% target remote <ip_address>:<port>
also there are arm-specific connection options if you have the
debugger compiled for remote debugging arm targets. After successful
connection the rest is the same as debugging on the host.
Bahadir
prev parent reply other threads:[~2007-02-14 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 12:04 Rakesh Kumar
2007-02-14 12:42 ` Daniel Jacobowitz
2007-02-14 15:32 ` Bahadir Balban [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ac1e90c0702140704w6376607dt247f1dafca230b05@mail.gmail.com \
--to=bahadir.balban@gmail.com \
--cc=gdb@sourceware.org \
--cc=hkrakeshkumar@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox