Message-ID: Date: Tue, 2 Mar 1999 18:26:30 +0000 To: djgpp AT delorie DOT com From: Dave Bird Subject: Mail delivery failed: returning message to sender MIME-Version: 1.0 X-Mailer: Turnpike (32) Version 4.01 Reply-To: djgpp AT delorie DOT com In message , Mail Delivery System writes >This message was created automatically by mail delivery software. > >A message that you sent could not be delivered to all of its recipients. The >following address(es) failed: > > djgpp AT delorie DOT com: > SMTP error from remote mailer after end of data: > host delorie.com [208.7.170.162]: > 500 Hey, offensive language ("d***ed") is not allowed. This is very silly, as d***ed is hardly very offensive. >In message , Eli Zaretskii: >>On Wed, 24 Feb 1999, Dave Bird wrote: >>> > > Hi. First of all, various messages have crossed in time and > caused a lot of confusion. I'm going to sit down and do what > I can until Monday, rather than just keep endlessly debating > with the DJ team by email which is not getting either side much > forrarder. I assume everyone will get this reply from the list. > >>> At the moment there is a program prefix at START: which >>> [description of what my current assembler start-up does] >> >>DJGPP's startup code and low-level library functions already do all >>that for you, > > Agreed, so what I do is define a replacement prefix as a > DJ-GPP program which then calls ASM_MAIN. > >>> Would RHIDE's GDB type debugger be happy with this? it would >>> just follow the source across into filename.S which >>> contained ASM_MAIN ?? >> >>I think somebody said that NASM cannot yet generate debug info, so you >>might need to use Gas (and hence the AT&T syntax) to get full debug >>support in assembly code. > > OK, checked that. Certainly NASM, inline Gas assembler, and > I assume (is this true?) also external Gas programs don't > generate debug line-number info, so I would have to do it > "by hand" or by writing a program. > >In message , Eli Zaretskii > writes >>On Wed, 24 Feb 1999, Dave Bird wrote: >> >>> OK: a prefix written in C could do all these things then call ASM_MAIN, >>> which is (unavoidably) written in Intel assembler by someone else. >> >>There are converters from Intel to AT&T style. Check out section 17.2 >>of the DJGPP FAQ list for several solutions. >> >>> Looks like that line-number info for inline assem will have to be >>> generated "by hand", or by writing a program myself to do it. >> >>That's only when the assembly code is inlined in a C source. Pure >>assembly modules are free from this problem, I think. > > OK, I'll try an external Gas program. > >In message, Salvador Eduardo Tropea writes: >>Dave wrote: >>> >RHIDE 1.4.7 can debug assembler with the dissasembler window. If you want to >>> >step in the .S file you'll need to add debug information to this file by >>> >hand. >>> >>> Yuck, that is truly awful --how do I add the debug information by hand?? >>> (either how to do it,or what webpages/infos I must read to find out how) >> >>Look in the info documents for gas, as and gcc (you can read it from RHIDE >>and they will look like Borland helps). >>Additionally you can try using the -S switch to see the assembler output of >>the compiler and learn how the debug information is added. > > I'll try looking at the compiler output for the nature of debug info. > >>> Is there any way to do it which fits more easily and sensibly with >>> the DJGPP way of doing things...... would it have debug info .S if it >>> were an AS file in backwards-format assembler? >> >>There is not automatic way. Inline assembler is pasted in the assembler >>output "AS-IS", nothing is added or removed. And without debug information >>you can't step in the sources, only in the disassembler window. > >~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~URLs > >In message , Eli Zaretskii > writes >>> Can you give me a current URL for this dead link too, please, >>> as I guess I'll be needing it soon. >> >>The URL is unchanged, it's just that the server seems to retire the >>document from time to time. >> >>> P.S. is this URL >>> OK for "ed"? >>No, Use this: >> ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/ed-02b.zip > > Thanks, I will. Brennan's page sure looks like a dead parrot----> > >On c.o.m.d, In article, <36D46BA6 DOT 6AB4 AT erols DOT com>, John S. Fine writes: >>Paradox wrote: >>> his page fell though. Does some one else know the location of another >>> tutorial site or the location of Brennan's new page? >> >>A copy (not new) of Brennan's tutorial: >>http://www.rt.e-technik.tu-darmstadt.de/~georg/djgpp/djgpp_asm.html > > I got it from there. Perhaps there could (eventually) be > an alternate link in the FAQ, if the first is erratic? > >In message <19990225063207 DOT AAA7776 AT jackal DOT intekom DOT com DOT intekom DOT co DOT za>, >StefanViljoen,6599 writes >>---------- >>Dave, >> >>Please go and visit my WWW page http://home.intekom.com/rylan/ and go to >>the programming section. I have done EXACTLY what you seem to want to do, >>i. e. convert assembly programs (mainly graphics demos) from TASM to NASM >>in protected mode under DJGPP > > This sounds like it might be my salvation; I will study up > on what Stefan has done. > -- __ .,-;-;-,. /'_\ : They seek her here, they seek her there, : _/_/_/_|_\_\) / : those critics seek her everywhere --- : '-<_><_><_><_>=/\ : is she in LA or gone for a swim, : jgs `/_/====/_/-'\_\ : that d***ed elusive Terrapin ? : ........"".....""....""..:>>>>>>>>>>> WHO IS THE MOCK TURTLE <<<<<<<<< {a href="http://www.xemu.demon.co.uk/clam/people/turtle.html"}????{/a}