From: Klaus Zeitler <Klaus.Zeitler@alcatel-lucent.com>
To: Pedro Alves <palves@redhat.com>
Cc: <gdb@sourceware.org>
Subject: Re: Shared library call problems on PowerPC with gdb 7.2
Date: Wed, 17 Apr 2013 07:55:00 -0000 [thread overview]
Message-ID: <q5gsj2plhgz.fsf@destgd0d00539.de.alcatel-lucent.com> (raw)
In-Reply-To: <516C1102.60208@redhat.com> (Pedro Alves's message of "Mon, 15 Apr 2013 15:38:58 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro>
Pedro> On 04/15/2013 03:20 PM, Klaus Zeitler wrote:
>> I'm using gdb 7.2, the exact version is:
>> GNU gdb (Wind River Linux Sourcery G++ 4.4a-341) 7.2.50.20100908-cvs
>> Maybe the gcc/binutils version is also relevant:
>> powerpc-wrs-linux-gnu-gcc (Wind River Linux Sourcery G++ 4.4a-341) 4.4.1
Pedro>
Pedro> You should request support from Wind River.
Did that November last year. I've exchanged many emails with Windriver,
but so far we haven't made any progress. That's why I thought that maybe
asking the real gdb experts here could help. Because from the info I
gathered in the internet, I thought this problem was already solved with
a patch for 6.8.
So of course the question remains, if and when (i.e. which version)
the patch went upstream into the sources.
And I also hoped that maybe there's some workaround for the version 7.2
we are using.
Pedro> You could also try a current/recent pristine FSF/GNU GDB.
Pedro> We're about to release 7.6.
Ok, I'll give 7.5.1 a try in the next days.
Thanks
Klaus
--
-------------------------------------------------------------------
| Klaus Zeitler Alcatel-Lucent |
| Lorenzstrasse 10 70435 Stuttgart, Germany |
| Department: Building: 005 Office: 3/171 |
| Telefon: +49 711821 43898 |
| Email: klaus.zeitler@alcatel-lucent.com |
| |
| Alcatel-Lucent Deutschland AG |
| Sitz der Gesellschaft: Stuttgart · Amtsgericht Stuttgart HRB 4026 |
| Vorsitzender des Aufsichtsrates: Michael Oppenhoff |
| Vorstand: |
| Alf Henryk Wulf (Vorsitzender) · Dr. Rainer Fechner |
-------------------------------------------------------------------
---
There are two ways to write error-free programs. Only the third one works.
next prev parent reply other threads:[~2013-04-17 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 14:21 Klaus Zeitler
2013-04-15 14:39 ` Pedro Alves
2013-04-17 7:55 ` Klaus Zeitler [this message]
2013-04-17 9:48 ` Pedro Alves
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=q5gsj2plhgz.fsf@destgd0d00539.de.alcatel-lucent.com \
--to=klaus.zeitler@alcatel-lucent.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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