Is GDB 4.16 the recommended version for egcs 1.0.2 ?

[Michael Meissner]

Jeffrey A Law writes:
| 
|   In message < Pine.LNX.3.95.980408174828.6568A-600000@voyager.home-of-linux.com write:
|   > I've got some strange problems with gdb. I'm using
|   > binutils-2.8.1.0.23 (compiled with egcs), egcs 1.0.2 (recompiled
|   > with itself), glibc 2.0.7 (compiled with gcc 2.8.1) and gdb 4.16
|   > (compiled with egcs) on a Linux box.
|   > 
|   > I'm writing a library called libgtop and an example program
|   > 'first' that uses that libray. This example program is
|   > statically linked with that library (libgtop.so and 
|   > libgtop_common.so are both part of that library, glibtop_open
|   > and glibtop_read are defined in glibtop.so):
| Right now gdb-4.16 is the recommended version.  It may be beneficial
| to use the "-gstabs++" option when building programs to ensure that
| you get stabs and not dwarf1 or dwarf2.

Actually, until 4.17 comes out, you might want -gstabs rather than
-gstabs++, since the stab format seems to have changed slightly.

| As soon as gdb-4.17 is released (in beta test right now) it will
| become the debugger of choice, largly due to its vastly improved
| dwarf2 support.
| 
| I see that you're trying to debug through a fork().  I do not
| believe gdb handles this well, if at all.
| 
| jeff