This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gdb and g77
- To: craig at jcb-sc dot com
- Subject: Re: gdb and g77
- From: Tim Schmielau <tim at rabe dot physik3 dot uni-rostock dot de>
- Date: Wed, 16 Jun 1999 01:04:46 +0200 (MEST)
- cc: egcs at egcs dot cygnus dot com
> Hmm, I consider gdb to *not* be working with pgf77.
> [...]
> Perhaps pgf77 works around one bug in gdb and hits another, while g77
> happens to do the opposite.
Yup, pgf77's code fails printing the whole array,
(gdb) print x
$17 = (( 1.10000002, 2.0999999, 3.0999999, 4.0999999, 5.0999999,
1.20000005) ( 2.20000005, 3.20000005, 4.19999981, 5.19999981,1.29999995,
2.29999995) ( 3.29999995, 4.30000019, 5.30000019, 1.39999998, 2.4000001,
3.4000001) ( 4.4000001, 5.4000001, 1.5, 2.5, 3.5, 4.5) ( 5.5,
1.60000002, 2.5999999, 3.5999999, 4.5999999, 5.5999999) )
while g77's succeeds
(gdb) print x
$2 = (( 1.10000002, 2.0999999, 3.0999999, 4.0999999, 5.0999999) (
1.20000005, 2.20000005, 3.20000005, 4.19999981, 5.19999981) (
1.29999995, 2.29999995, 3.29999995, 4.30000019, 5.30000019) (
1.39999998, 2.4000001, 3.4000001, 4.4000001, 5.4000001) ( 1.5, 2.5, 3.5,
4.5, 5.5) ( 1.60000002, 2.5999999, 3.5999999, 4.5999999, 5.5999999) )
So there really seems to be no way of teaching gdb both things.
By the way, PG's own debugger pgdbg works correctly on both pgf77's
and g77's code, so they seem to have done a fairly complete workaround (as
far as possible).
This suggests they also have investigated this point and haven't found a
better way of teaching gdb, either.
Tim Schmielau (tim@physik3.uni-rostock.de)