From: "The Westlakers" <westlakers@gmail.com>
To: "The Westlakers" <westlakers@gmail.com>, gdb@sourceware.org
Subject: Re: question about GDB message
Date: Tue, 25 Sep 2007 11:48:00 -0000 [thread overview]
Message-ID: <6b14b5b00709250441v6e04f36bm1553dc901ecb6e17@mail.gmail.com> (raw)
In-Reply-To: <20070925110500.GA29300@caradoc.them.org>
On 9/25/07, Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Sep 25, 2007 at 12:28:40PM +0800, The Westlakers wrote:
> > Hi GDB experts,
> >
> > I am having problem when I made "target remote:192.1.1.255:6000"
> > I can see the packets being sent to the remote target machine, and replied
> >
> > with right reponding packets. But after that, it prints out:
> >
> > procfs: couldn't find pid 42000 in procinfo list.
> >
> > then can not do anything from there.
>
> How did you configure GDB? It should probably be sparc64-elf if you
> are connecting to a no-OS target.
>
Yes, it is 64 bit ELF. just run gdb on Solaris host and typed the remote target
command.
1) I can run 32-bit GDB to get reg file and thread info from the
target, even if
the image running in the target is 64-bit, I managed to talk in 32-bit.
2) However when run 64-bit GDB, I got the procfs problem.
Why GDB 64-bit needs procfs?
> --
> Daniel Jacobowitz
> CodeSourcery
>
next prev parent reply other threads:[~2007-09-25 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6b14b5b00709242126n5321100m2aad74fd7c7ea58d@mail.gmail.com>
2007-09-25 11:05 ` The Westlakers
2007-09-25 11:41 ` Daniel Jacobowitz
2007-09-25 11:48 ` The Westlakers [this message]
2007-09-25 12:27 ` Daniel Jacobowitz
2007-09-25 12:35 ` The Westlakers
2007-09-25 14:10 ` Daniel Jacobowitz
2007-09-25 16:03 ` The Westlakers
2007-09-25 16:31 ` Daniel Jacobowitz
2007-09-25 16:38 ` The Westlakers
2007-09-25 16:45 ` Daniel Jacobowitz
2007-09-25 16:54 ` The Westlakers
2007-09-25 17:22 ` Daniel Jacobowitz
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=6b14b5b00709250441v6e04f36bm1553dc901ecb6e17@mail.gmail.com \
--to=westlakers@gmail.com \
--cc=gdb@sourceware.org \
/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