From: broeker AT physik DOT rwth-aachen DOT de Newsgroups: comp.os.msdos.djgpp Subject: Re: HELP! : Debugging a c/asm mixed programs Date: 29 Mar 2000 12:52:41 GMT Organization: Aachen University of Technology (RWTH) Lines: 46 Message-ID: <8bsuap$j9q$1@nets3.rz.RWTH-Aachen.DE> References: <19464ea8 DOT 15fd37ca AT usw-ex0105-036 DOT remarq DOT com> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 954334361 19770 137.226.32.75 (29 Mar 2000 12:52:41 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 29 Mar 2000 12:52:41 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com batchex wrote: > I usually use FSDB to debug the ASM modules, but now I face 2 > problems. One, if I use NASM's structure support in the ASM > modules, FSDB randomly throws an exception. I don't know what that structure support does, but it should *never* cause any difference in behaviour of FSDB if you use it or not. Especially since NASM, as you say, does not generate any debug info at all. I.e. the only output it generates is raw code and data, as far as FSDB is concerned. It should never make any difference how that code was described, to NASM. If it does, my guess is that constitutes a bug either in NASM, or in your way of using it. > I have tried GDB, but because NASM doesn't support debug info > with COFF format yet, it can't 'step' into the function. The ASM > function is called as a whole and it can't run single-step. You should still be able to 'stepi', i.e. single-step in terms of assembly operations. GDB won't display any source code, but if you 'disassemble' your routine, first, you'll still know where you are. You can also 'info reg' to see the register contents. Not very convenient, but you can do it. > How can I debug these (ASM) functions? Does anybody know FSDB's > official site? There is none, AFAIK. FSDB is part of DJGPP, not a separate project. > or even if it is still supported? Well, if you have a patch for it, we'll gratefully put it into the DJGPP sources. But no-one seems to be actively working on FSDB, any more. Wether that makes it an 'supported' or 'unsupported' program is a matter of taste, I'd say. > Are there any other debugger like FSDB which can handle DJGPP/NASM > compiled programs? Well, there's always 'edebug32', the first debugger DJGPP ever had. It's still there, but its debug information support is exactly the same as FSDB (they share the code), so any fundamental problems hitting FSDB have a good chance to disable edebug32, too. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.