From: "Kevin B. Hendricks" <kbhend@dogwood.tyler.wm.edu>
To: gdb@cygnus.com
Subject: Problems with 4.16.86 under linux ppc / mklinux, etc
Date: Tue, 31 Mar 1998 13:11:00 -0000 [thread overview]
Message-ID: <v03110704b1470a7a62e7@[128.239.12.89]> (raw)
Hi,
I work on the team porting Sun JDK to linuxppc, mklinux, linux-pmac. These
ports have generally chosen to use egcs-1.0.2 since it is much better then
gcc-2.7.2 on powerpc and does not have the problems gcc-2.8 has on powerpc.
Unfortunately, the gdb 4.16 that previously worked under gcc -2.7.2 does
not work any longer with things compiled with the new tools (egcs-1.0.2,
binutils-2.8.1.0.20, etc
I have recently downloaded, patched and built gdb 4.16.86 to work under
linux on powerpc (with the help of Kevin Buettner) but the result is next
to worthless when trying to debug anything with shared-libraries (skipped
breakpoints, missing symbols, general instability).
Following the FAQ of egcs, I have tried compiling things with -gstabs which
did not help at all either.
Do you have any timetable for getting gdb 4.17 out? We desperately need a
working gdb. I would be happy to make our gdb diffs for powerpc available
to you if it would help. Also I would be happy to act as a tester on linux
for powerpc.
If there is anything I can do to speed the process of getting a working gdb
4.17, please let me know.
Thanks,
Kevin
--------------------------------------------------------------------------
Kevin B. Hendricks
Associate Professor of Operations and Information Technology
School of Business, College of William & Mary, 307 Tyler Hall,
P.O.Box 8795, Williamsburg, VA 23187-8795
(757) 221-1702, kbhend@dogwood.tyler.wm.edu; http://business.tyler.wm.edu
reply other threads:[~1998-03-31 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='v03110704b1470a7a62e7@[128.239.12.89]' \
--to=kbhend@dogwood.tyler.wm.edu \
--cc=gdb@cygnus.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