www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/03/09/14:01:00

Message-ID: <fBnFVAAa+W52EwKc@xemu.demon.co.uk>
Date: Tue, 9 Mar 1999 18:59:38 +0000
To: djgpp AT delorie DOT com
From: Dave Bird <dave AT xemu DOT demon DOT co DOT uk>
Subject: tracing into assmbler, how?
MIME-Version: 1.0
X-Mailer: Turnpike (32) Version 4.01 <dQumtnY$x4rJ2u5tL5fS$n2vuP>
Reply-To: djgpp AT delorie DOT com

In me<m10G4bV-000S6GC AT inti DOT gov DOT ar>, 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.
> 
>> 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?  if the assembly code
>> were inlined into the C program?   or is there simply no way ever
>> it will automatically add the debug info to the assembler code?
>
>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.

 Thanks for the above.  I wondered whether it was possible to get
 proper source and symbolic debugging of assembler files when they are
 (1A) included AS    -- no, that fails to single step assembler parts
 (1B) external AS    -- that also fails to single step.
 (2)  external NASM  -- that also fails to single step.

 You said (1B) would probably work if I put in debug information
 [which I could get by looking at compiler output with a -S switch]
 in there by hand.

 I've tried that, it doesn't work yet.  Any suggestions what I'm 
 doing wrong?   I copied all the debug stuff I find in a compiler
 output file, into the AS file. Still no joy.  What's wrong now?

 Source included, very minimal at 50 lines in all.
 [NOT to mailing-list/newsgroup because of previous hassle and
 flaming, write to me for a copy].

-- 
   ^-^-^-@@-^-;-^   http://www.xemu.demon.co.uk/
        (..)__u     news:alt.smoking.mooses

       happy as a clam at high tide -. <_" .-._.-.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019