[comp.sys.ibm.pc] Microsoft LINK Bug -- Have You Run Into This One Yet?

cramer@optilink.UUCP (Clayton Cramer) (09/16/88)

I'm using C V5.1, and LINK V3.65, and I'm getting:

    fatal error L1103: attempt to access data outside segment bounds

This only happens if I specify the /CODEVIEW switch to the linker.
At Microsoft Tech Support's request, I have done all the following:

1. Recompiled all modules with the /Gt0 switch (forces all the data into
FAR_DATA class segments for all modules, reducing the size of the DGROUP,
which is FAR lesss than 64K).

2. Recompiled all modules with all TSRs removed (yes, I thought they
were grasping for straws on this also).

On my initiative, I've done the following:

1. Recompiled all modules with no debugging information.

2. Enlarged the number of segments with the /SEGMENTS:256 switch.

Rearranging the order of the .OBJ modules input to the linker moves the
associated module for the error message.  With the /CODEVIEW switch
removed, it links OK (of course, then I can't debug it).

In theory, someone more knowledgeable about LINK will call me back from
Microsoft, but since, at their suggestion, I sent the last problem I
had with Microsoft LINK (overlaid functions resolving to DS:0) almost
two months ago, and have heard nothing at all, I'm not holding my
breath.

Have you run into this problem, and have you figured out how to solve it?
-- 
Clayton E. Cramer
..!ames!pyramid!kontron!optilin!cramer