From: "John S. Fine" <johnfine AT erols DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: linking problem (?) with ASM & C files
Date: Sun, 07 Nov 1999 13:00:09 -0500
Lines: 18
Message-ID: <3825BE29.C46@erols.com>
References: <8011ai$9db$1 AT nnrp1 DOT deja DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: TmnOuzeoUqQHWvtZa3HMchGaR7ysHTAXK3La2CWe/HY=
X-Complaints-To: abuse AT rcn DOT com
NNTP-Posting-Date: 7 Nov 1999 18:02:49 GMT
X-Mailer:  Mozilla 3.01 (Win95; U)
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Mavi Gozler wrote:

> 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
. . .
> 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 (!!).

  That sounds like the error you get if you don't give the code segment
in your ASM source exactly the same name that DJGPP gives the code
segment.  I think that name is ".text"
-- 
http://www.erols.com/johnfine/
http://www.geocities.com/SiliconValley/Peaks/8600/