Mail Archives: djgpp/1999/02/24/18:01:16
In message<m10FicP-000S6rC AT inti DOT gov DOT ar>, Salvador Eduardo Tropea writes:
>Dave Bird <dave AT xemu DOT demon DOT co DOT uk> wrote:
>>
>> Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> writes:
>> |On Tue, 23 Feb 1999, Dave Bird wrote:
>> ||
>> || OK, I'll try rhino-hide....
>
>Is RHIDE, not rhino-hide, nobody is hidded and no rhino too.
I'll take your word for it.
>> (i.e. without needing
>> to stop and learn a whole new IDE).
>
>:-))))), RHIDE is a BC++ 3.1 IDE clone, if you know how to use Borland's IDE
>learning RHIDE is very easy.
Ah, that's good.
>> |From this description, it should become clear that the DJGPP debugg-
>> |ers are probably not good for debugging anything but DJGPP programs,
>> |or programs that at least look and behave like DJGPP ones.
>>
>> Right. From this it is clear that the simplest and most sensible
>> way to achieve what I want is to make the prefix a 'C' program
>> which then calls asm_main rewritten in [Nasm] assembler.
[............]
>That's a lot of work you don't need to do. Do it in C with DJGPP and left the
>assembler for the really important stuff.
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.
>> Next it defines wrappers for various DOS calls with convenient
>> register-passing conventions for WriteChar, WriteString, [.....]
>> I suppose this is what I would want to do with the prefix
>> written in C, with a call to ASM_MAIN.
>> Would RHIDE's GDB type debugger be happy with this? it would
>> just follow the source across into name.S which contained ASM_MAIN ??
>
>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)
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?
Hmm, FAQ:
:
: One problem with this translation is that it relies on info generated
: by GCC that maps the instruction addresses to source line numbers.
: This usually works okay, but one notable exception is when you use
: inline assembly. In this case, GCC only records the last line of the
: inline assembly block, which might be way off if the block is large.
:
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.
:
: A guide is available which was written by Brennan Underwood;
: it describes how to use inline assembly programming with DJGPP
: and includes a tutorial on the AT&T assembly syntax. Check out
: the __DJGPP inline assembly tutorial__ .
:
Can you give me a current URL for this dead link too, please,
as I guess I'll be needing it soon.
P.S. is this URL
ftp://ftp.delorie.com/pub/djgpp/v2gnu/ed-02b.zip
OK for "ed"? I'm just going to log on and try it.
====================
An FTP protocol error occurred while trying to retrieve the URL:
ftp://ftp.delorie.com/pub/djgpp/v2gnu/ed-02b.zip
Squid sent the following FTP command:
CWD v2gnu
and then received this reply
v2gnu: No such file or directory.
===============No, try elsewhere
--
^-^-^-@@-^-;-^ http://www.xemu.demon.co.uk/
(..)__u news:alt.smoking.mooses
happy as a clam at high tide -. <_" .-._.-.
- Raw text -