From: Kent Borg <kentborg@borg.org>
To: Kenneth Johansson <kenneth.johansson@etx.ericsson.se>
Cc: Jean-Denis Boyer <jdboyer@m5t.com>,
"linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: ptrace Problem
Date: Wed, 16 Jul 2003 10:26:57 -0400 [thread overview]
Message-ID: <20030716102657.D20719@borg.org> (raw)
In-Reply-To: <1058351871.31114.26.camel@spawn>; from kenneth.johansson@etx.ericsson.se on Wed, Jul 16, 2003 at 12:37:51PM +0200
On Wed, Jul 16, 2003 at 12:37:51PM +0200, Kenneth Johansson wrote:
>
> On Tue, 2003-07-15 at 23:49, Kent Borg wrote:
>
> > Looking at likely source tarballs we have sitting around it seems very
> > likely that binutils were built from 2.13.2.1, and glibc 2.3.2. (How
> > can I be sure?)
>
> binutils binaries usually respond with the version when given -V on the
> command line.
Oh! I thought that was a version of an individual component, but
lordy, nm and objdump both give the same number and it matches the tar
I had guessed we had used.
> libc can be checked with objdump -x and checking the Version
> definitions.
It lists a series of numbers ranging from 2.0 to 2.2.2.
> This should not be a problem gdb dose all the work using ptrace.
Indeed, gdb didn't drag me down into any libraries.
> Regarding your gdb problems have you tried with a kernel without bdi2000
> support in the kernel.
No, but I will now.
Thanks,
-kb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-16 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 16:30 ptrace Problem Jean-Denis Boyer
2003-07-15 21:49 ` Kent Borg
2003-07-16 10:37 ` Kenneth Johansson
2003-07-16 14:26 ` Kent Borg [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-16 19:46 Jean-Denis Boyer
2003-07-15 15:43 Kent Borg
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=20030716102657.D20719@borg.org \
--to=kentborg@borg.org \
--cc=jdboyer@m5t.com \
--cc=kenneth.johansson@etx.ericsson.se \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).