Date: Fri, 12 Mar 1993 15:33:34 +0100
From: Dirk Zabel <dzabel AT cs DOT tu-berlin DOT de>
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: go32

Hi,
There have be some messages about problems with debug32 (mainly bad
documentation), but I have encountered other difficulties:
1. debug32 can't read in large source files; i.e. if I have
   not 10 source files 200 lines each but one with 2000 lines, I
   get an out of memory error and debug32 quits.
2. Sometimes I get plain wrong object-address-to-source-line mappings
3. There are cases where symbol reading at startup is very slow

As far as I can see, (1) results from trying to read the whole source file
in one big chunk into real mode memory before it is copied into virtuel
memory. Unfortunately, I can't change this since I don't have Turbo C and
Turbo Assembler.

Point (2) is inexplicable to me. If I manage to get a small example, I might
send it to D.J. Delorie or send it to this mailing list.

Point (3) is not very severe; it occurres if I try to debug a program which
was originally written in Modula-2 and converted to C using mtc (a nice
Modula-2 to C converter obtainable from ftp.karlsruhe.gmd.de [192.76.241.33]).
This converter generates symbol names like Inout_WriteLn, Inout_Write etc from
procedures WriteLn and Write inside module InOut, so I guess the hashing scheme
used by debug32 breaks down to some linear search. 

I would like to know wether somebody else also experienced problems (1) and (2).

-- Dirk

P.S. I still use djgpp 1.08; maybe those difficulties have vanished in 
     version 1.09?!?