CompuServe Messages

Doug, Well, I did contact tech support, & they thought maybe one particular object module might be causing the problem, so I started breaking my library in halves, in hopes of isolating one module eventually. The original library was a little over 300k in size. When I got the parts down to < 150k, it worked fine…. no changes to c code or options or anything. The original weirdness with codeprobe is still around, and I do have a small test program which shows the situation…. Don't know when I'll get a chance to send it off to SAS; my current priorities are to get more functions working & this is more of a puzzle than a roadblock. One other "interesting" thing: before I was using oml, I had about a half dozen .o files which were included in the link command… I broke the sources up into individual files ( one function per source file instead of several ), and built my libraries from the resulting 50+ .o files. Now when I link, the resulting executable has grown from originally a little over 300 k to over 600 k. I had expected no change or slightly smaller, since there were a couple of functions in the original big object modules which weren't yet used. Does the linker allign modules in some way that would cause this? ( many of my new modules are quite small, only a line or to of c code in several cases. ) Thanks for the help.