From: Mavi Gozler Newsgroups: comp.os.msdos.djgpp Subject: linking problem (?) with ASM & C files Date: Sat, 06 Nov 1999 10:53:06 GMT Organization: Deja.com - Before you buy. Lines: 30 Message-ID: <8011ai$9db$1@nnrp1.deja.com> NNTP-Posting-Host: 195.112.128.222 X-Article-Creation-Date: Sat Nov 06 10:53:06 1999 GMT X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 95; DigExt) X-Http-Proxy: 1.1 proxy02.ada.net.tr:80 (Squid/2.2.STABLE5), 1.0 x35.deja.com:80 (Squid/1.1.22) for client 195.112.142.189, 195.112.128.222 X-MyDeja-Info: XMYDJUIDbuyuk_yarak To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com It seems whenever I have linked an ASM file with my C files, I get what I want in terms of a properly built program. But now I am seeing something weird. I have this module with a function called mkdirp() in ASM form, which RHIDE automatically builds with NASM, and there is no problem. I have defined _mkdirp as a global so it gets exported, and it gets built in with the rest of my C files. Now I want to debug/follow it in RHIDE's dissassembly window, which I call up when the trace line in on the function. But when I step into the function, the code is absolutely different from what even objdump shows is there. What's more, if I run it again and again and step into it, the code that appears in the dissembly window is different every time (!!). This seems totally bizarre to me. If I leave the ASM file out of the project, an undefined reference to _mkdirp is reported, what I'd expect. The NASM manual doesn't offer a clue, and neither does the DJGPP FAQ. For the C files I have set only the -g debugging compiler flag, in addition to the usual warning flags; nothing else that would tend to generate code at the start of end of function calls. Can anyone offer suggestions for what I should look at?? Thanks Sent via Deja.com http://www.deja.com/ Before you buy.