young@wglen.UUCP (Randy Young) (10/22/90)
Hello: I am having a small problem with Blink. I am working on a game for the amiga. The game consist of about 17 source modules. One of the source files is named task.c, when I use Blink to link the object files together it seams to work OK. But when i run the program it just hangs at the CLI, the code in the task.o file is mostly in comments, and does'nt ever get called. Is "task" a keywork or something important to Blink. If I don't link in the task.o module then the program opens it custom screen as expected. I am not sure of the problem, if anybody has any advice on what to do please write. The program is being compiled on a A2000 under SAS/C 5.1, the code size is around 300K. Tanks in advance Randy Young
walker@unx.sas.com (Doug Walker) (11/07/90)
In article <247@wglen.UUCP> young@wglen.UUCP (Randy Young) writes: >Hello: > >I am having a small problem with Blink. I am working on a game for the >amiga. The game consist of about 17 source modules. One of the source >files is named task.c, when I use Blink to link the object files together >it seams to work OK. But when i run the program it just hangs at the CLI, >the code in the task.o file is mostly in comments, and does'nt ever get >called. Is "task" a keywork or something important to Blink. If I don't >link in the task.o module then the program opens it custom screen as >expected. I am not sure of the problem, if anybody has any advice on what >to do please write. The program is being compiled on a A2000 under SAS/C >5.1, the code size is around 300K. > >Tanks in advance >Randy Young Task is not a keyword to BLINK as far as I know. (You could test it by renaming the module temporarily, though). There's not really enough information in your posting to figure out the problem, so please contact SAS/C Technical support at (919)677-8009 (9am-5pm EST) or FAX them at (919)677-8123. You can also write to Amiga C Technical Support SAS Institute, Inc. SAS Campus Drive Cary, NC 27513 A few things to have in hand when you call: your serial number (of course), your compile options, your link options, and any errors or warnings that your code produced when compiled or linked. You might also try debugging it with CPR and the -w option, which tells CPR not to run the startup code. You can then single-step through the startup code and figure out where it runs into trouble. ***** =*|_o_o|\\=====Doug Walker, Software Distiller====== BBS: (919)460-7430 = *|. o.| || 1200/2400/9600 Dual | o |// For all you do, this bug's for you! ====== usenet: ...mcnc!rti!sas!walker plink: dwalker bix: djwalker