From: Gary Thomas <gdt@linuxppc.org>
To: Kevin Buettner <kev@primenet.com>
Cc: linuxppc-dev@lists.linuxppc.org
Cc: linuxppc-dev@lists.linuxppc.org,
Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
"Kevin B. Hendricks" <kbhend@business.wm.edu>
Subject: Re: gdb broken under linuxppc r5 tools
Date: Mon, 02 Aug 1999 05:20:54 -0600 (MDT) [thread overview]
Message-ID: <XFMail.990802052054.gdt@linuxppc.org> (raw)
In-Reply-To: <990801202455.ZM22552@redrock.lan>
On 01-Aug-99 Kevin Buettner wrote:
>
> On Aug 1, 9:03pm, Franz Sirl wrote:
>
>> Am Son, 01 Aug 1999 schrieb Kevin B. Hendricks:
>> >Hey,
>> >
>> >Does anyone know what's up with gdb lately? It used to be quite stable but
>> >since I upgraded to the glibc, binutils, egcs, gdb from Linuxppc R5 cd, I
>> >can't seem to set any breakpoints in shared libraries (or they show up
>> >someplace else at random). Functions are missing (or don't show up) and if
>> >I try to disassemble one function in a shared library, I often get another.
>> >
>> >I really need a working stable gdb.
>> >
>> >Has anyone else run into this. If so, exactly what versions of gdb, glibc,
>> >binutils, egcs are stable together, especially when working with shared
>> >libraries?
>>
>> Well, you've hit one of our weakest points here. AFAIK there's currently
>> nobody
>> taking care of gdb on Linux/PPC. In fact we are lucky that Kevin Buettner's
>> old
>> patch could be converted to 4.17.x. Unfortunately it's still not integrated
>> into gdb's mainline due to copyright issues, so we have to reintegrate the
>> patch
>> in every new version :-(.
>>
>> So, is someone willing to take care of gdb on Linux/PPC?
>
> Kevin, Franz, et.al,
>
> Earlier this year, Metrowerks and I signed the copyright assignments
> required by the FSF. Beginning August 9, I will be starting work at
> Cygnus as a GDB engineer. One of the things that I'll work on is a
> merge of my patches into the current gdb mainline. It'll be my goal
> to get a solid, usable gdb up and running on Linux/PPC again.
>
Kevin B.,
Firstly, congratulations and welcome to the fold :-)
Secondly, while you're in there, can you look at my patches for GDB-4.18.
I've made a useable GDB for this version, with no input from any of the
4.17 patches BTW. They might be easier to make into a "clean" set for
the latest version. You can find my patches in the RPM I uploaded to
ftp://ftp.linuxppc.org/users/gdt/redhat/SRPMS
When you get something ready, let me know and I'll help check it out.
Thanks.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-02 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-01 13:01 current recommended versions of glibc/egcs/binutils for R5? R Shapiro
1999-08-01 13:58 ` Franz Sirl
1999-08-01 18:38 ` gdb broken under linuxppc r5 tools Kevin B. Hendricks
1999-08-01 19:03 ` Franz Sirl
1999-08-01 20:12 ` kbhend
1999-08-01 20:24 ` Kevin Buettner
1999-08-01 20:54 ` Franz Sirl
1999-08-02 11:20 ` Gary Thomas [this message]
1999-08-02 15:21 ` kbhend
1999-08-02 15:50 ` Daniel Jacobowitz
1999-08-02 16:01 ` kbhend
1999-08-22 15:09 ` bug in glibc 2.1.2 new semaphore functions in libpthread? Kevin Hendricks
1999-08-24 21:09 ` Franz Sirl
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=XFMail.990802052054.gdt@linuxppc.org \
--to=gdt@linuxppc.org \
--cc=kev@primenet.com \
--cc=linuxppc-dev@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).