From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: peter@baradas.org
Cc: drow@mvista.com, Peter.Barada@motorola.com,
gdb@sources.redhat.com, libc-alpha@sources.redhat.com
Subject: Re: Trouble with gdbserver from gdb-5.3, glibc-2.3.2 on ppc32
Date: Wed, 10 Sep 2003 17:41:00 -0000 [thread overview]
Message-ID: <200309101741.h8AHf6I06309@hyper.wm.sps.mot.com> (raw)
In-Reply-To: <20030910001816.95A739899C@baradas.org> (message from Peter Barada on Tue, 9 Sep 2003 20:18:16 -0400 (EDT))
>>on my native setup. This happens when debugging a particular
>>statically linked executable that was built against a different version
>>of linuxthreads than is present on my host. Is that binary statically
>>linked?
>
>No, its dynamically linked.
Now that the power is back on(and our network is up and runnig again),
I looked again and indeed its statically linked. I'll try dynamically
linking it and see what happens.
What's still strange is that the toolchain I used to build the
executable is the same on I used to build gdbserver...
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(A Motorola Company) 781-270-0193 (fax)
next prev parent reply other threads:[~2003-09-10 17:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 20:32 Peter Barada
2003-09-09 20:46 ` Roland McGrath
2003-09-09 21:15 ` Peter Barada
2003-09-09 21:24 ` Roland McGrath
2003-09-09 21:23 ` Daniel Jacobowitz
2003-09-09 21:30 ` Daniel Jacobowitz
2003-09-09 21:39 ` Roland McGrath
2003-09-09 21:40 ` Daniel Jacobowitz
2003-09-10 0:18 ` Peter Barada
2003-09-10 17:41 ` Peter Barada [this message]
2003-09-10 18:58 ` Peter Barada
2003-09-10 0:34 ` Peter Barada
2003-09-10 0:49 ` Dan Kegel
2003-09-10 0:53 ` Peter Barada
2003-09-09 21:45 ` Dan Kegel
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=200309101741.h8AHf6I06309@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=Peter.Barada@motorola.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=libc-alpha@sources.redhat.com \
--cc=peter@baradas.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