From: Quality Quorum <qqi@world.std.com>
To: Brijesh Shukla <iap_shukla@access.co.jp>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: remote debugging
Date: Fri, 13 Jun 2003 13:28:00 -0000 [thread overview]
Message-ID: <Pine.SGI.4.30.0306130924310.2754-100000@world.std.com> (raw)
In-Reply-To: <3EE9822C.8090209@access.co.jp>
On Fri, 13 Jun 2003, Brijesh Shukla wrote:
> Hello,
>
> Can any body explain the remote debugging application in Linux.
> currently for testing purpose as simple case, I have chosen two i686
> Pentium machines with Linux
> installed on two systems. on system I am running gdb and in another
> system I am running gdb server. I did the following steps.
>
> Target:
> gdbserver host:port program
>
> //Now gdbserver has been started
>
> Host:
>
> // I compiled the simple hello word program as gcc -g program.c -o
> program
> // copied the program into target system
>
> gdb program
> gdb> target remote host:port
> gdb>
>
> // connection established
> gdb> load
You should not do that, gdbserver already loaded the program.
The rest of your problems may be related to this step.
>
> // it is showing loading the sections, I m not sure the addresses from
> local machine or from target machine ( how can I verify ? in our
> case,sicne both machine
> are same architecture and same OS)
>
> I can set break point to main.
>
> if I do step or next, I am getting the error message "cannot find
> bounds of current function"
>
> if I do continue, I am getting the error message " program received
> SIGSEGV, segmentation fault"
>
> can anybody tell me where is the wrong ?
>
> Is there anything's need to be take care while building the gdb in one
> machine. ? currently I am using the default gdb installed in machine
> due to both machine are same architecture.
>
> Regards
> Brijesh Shukla
>
Thanks,
Aleksey
next prev parent reply other threads:[~2003-06-13 13:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 7:50 Brijesh Shukla
2003-06-13 13:28 ` Quality Quorum [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-07 13:52 Remote debugging Russell Shaw
2015-03-07 14:09 ` Ofir Cohen
2015-03-08 7:48 ` Russell Shaw
2004-03-22 14:23 luca risso
2004-03-19 17:59 luca risso
2004-03-19 18:43 ` Daniel Jacobowitz
2003-06-13 14:24 remote debugging nak26
2003-03-20 7:45 Patricia Alba
2002-12-12 9:29 Remote Debugging Tim
2002-12-12 10:30 ` Daniel Jacobowitz
2002-07-22 9:35 remote debugging Vinayak P Risbud
2001-01-25 5:27 malar kavi
2001-01-25 11:46 ` J.T. Conklin
2001-01-23 22:23 malar kavi
2001-01-24 6:16 ` Fernando Nasser
2001-01-24 10:52 ` J.T. Conklin
2000-11-30 22:27 Remote Debugging Yu Xuanwei
2000-12-01 11:40 ` Fernando Nasser
2000-11-29 19:52 Yu Xuanwei
2000-11-28 0:59 Remote debugging Yu Xuanwei
2000-08-15 10:13 remote debugging Shaun Jackman
2000-08-15 12:23 ` Fernando Nasser
2000-04-01 0:00 Remote Debugging Timo Ketola
2000-02-23 19:12 ` Andrew Cagney
2000-04-01 0:00 ` Andrew Cagney
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=Pine.SGI.4.30.0306130924310.2754-100000@world.std.com \
--to=qqi@world.std.com \
--cc=gdb@sources.redhat.com \
--cc=iap_shukla@access.co.jp \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).