🚀 go-pugleaf

Dirk C. Mattfeld
Computing Center
University of Bremen
2800 Bremen 41
Germany

<dcm@lrw.uni-bremen.de>


Dear bug-gdb!

I have trouble installing gdb 4.6 on a MACH 2.6 System delivered by MtXinu. 

MtXinu delivers their systems with gcc 1.37 and gdb 3.5. I recently
installed gcc 2.2.2 (wich works pretty well) and now I wanted to have
gdb 4.6. This installation failed until now!

I configured gdb via 'configure i386-aout-mach', what was the only
combination making sense to me. An error occured configuring the
./gdb-4.6/gdb directory. The file ./gdb-4.6/gdb/configure.in contains
two large 'case' structures: in the first the '.mh' file is selected,
in the second the '.mt' file is selected.  The configuration failed
because the file ./gdb-4.6/gdb/config/i386mach.mt is not present. It
seems strange to me, that there is a file ./gdb-4.6/gdb/config/i386mach.mh.

I tried to help myself using i386mach.mh and the i386aout.mt file,
because the a.out linker format is used on my kind of systems. When
this constallation did not work, i tried to find out what the
i386aout.mt file does. I hoped to find a suitable file out of a couple
of files named i386*.mt. Apart from System V.4 all the files configure
exec.o i386-tdep.o and i386-pinsn.o in the ./gdb-4.6/gdb directory.
Furter on they configure tm-i386v.h or tm-i386v-g.h. All that seems to
be COFF stuff and not a.out as expected.

So why do you specify a i386mach target without supporting the a.out
format for i386. Perhaps i am wrong in configuring this type of
system. Or something went wrong in your file dependencies. Let me know
if you have an idea to solve my problems.

What I have now: I copied the i386aout.mt to i386mach.mt and the
configure succeeded. The compilation succeded too, but the new gdb
cannot read symbol tables properly. programs can be run via gdb, but
of course, no beakpoints etc. can be set. Please help me!


Regards

Dirk C. Mattfeld