Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!usc!apple!vsi1!wyse!mips!ultra!srini
From: srini@ultra.com (S. Srinivasan)
Newsgroups: comp.os.msdos.programmer
Subject: MSC 6.0 does not execute lines of C code
Keywords: MSC 6.0 C Codeview
Message-ID: <1990Aug3.172039.250@ultra.com>
Date: 3 Aug 90 17:20:39 GMT
Organization: Ultra Network Technologies
Lines: 46

This is a posting for a friend who does not have net access
-----------------------------------------------------------

System: MSC 6.0, Medium Model, Multi-module(i.e. LINK used)
	on a '286-clone

There are occasions when writing 'C' code that a line of
code is just not executed at all.  For example, 

    *stepping in Codeview simply jumps over the source line!

    *cannot set breakpoint on source line in Codeview,
     it beeps back!!

Looking at the .COD file (produced by /Fc option?), 
which has both the 'C' source and 'ASM' lines, the correct 
ASM lines are generated.  So the culprit could be the
LINK-er, but there seems to be no way around the problem.
Sometimes retyping the whole function makes the problem go
away.  There is no pattern to this: it happens at the start
of a function, or in the middle of a function.

Once it was a call to an assembly routine:

	result = asm_routine();

and the problem went away when the routine was coded to work as:

	asm_routine(&result);

Another time it was a simple 'C' operation:

	variable = ~variable;

which refused to go away regardless of re-typing or anything else

-----------------------------------------------------------
Totally baffled !
Please respond to this account, and I will convince my friend
that USENET access is something worth shouting about.

Thanks a bunch,

srini@ultra.com
    -or-
...!ames!ultra.com!srini