Date: Tue, 23 Apr 1996 20:32:40 +0800 (GMT+0800) From: Orlando Andico To: Marc Singer Cc: naderr AT topaz DOT cqu DOT edu DOT au, DJGPP List Alias Subject: Re: Standard 32-bit libraries In-Reply-To: <199604240036.RAA12597@netcom8.netcom.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 23 Apr 1996, Marc Singer wrote: > > > > elf AT netcom DOT com writes: > > > Good question. It seems to me that going to ELF would be better since > > > it is a better designed format than COFF. > > > > > > Marc Singer > > > > Hmm, and maybe we get to IBCS2 ( Intel Binary Code Standard ) as well, so > > that we may run Linux,SCO, etc ELF binaries ... that would be > > good :) > > Yer kidding, right? ELF should not be too bad since the binutils > package already supports it. The DJGPP loader could load the segments > and away you go. Debug info is another question, but I believe that > ELF does it better than COFF. > > Marc Singer > That was the subject of my original post, actually. I don't think DJGPP can embed enough debugging info in the binary, so you can't debug across multiple source files. I use the exact same gcc under Solaris (ELF), and both AOUT and ELF Linux machines, and they *can* debug across multiple source files. Try doing that with DJGPP. Someone suggested that what we have is an old GDB (it is), but someone else said that the old versions of DJGPP (which produced a.out files by default) could do it. I can't try this out 'cause my old DJGPP is gone and I didn't know to use GDB then ;) However: it says in the gcc documentation that you can build the compiler to attach stabs debugging info in the COFF binary. If I rebuild the compiler with this option, will I then be able to debug multiple source files? Cheers, Orlando Andico orly AT abigail DOT eee DOT upd DOT edu DOT ph