thomas@eleazar.dartmouth.edu (Thomas Summerall) (08/21/90)
Is there a list somewhere of the init that THINK C 4.0 has problems with? I am experiencing some weird stuff that I think must be init problems... Thanks, Thomas Summerall thomas@eleazar.dartmouth.edu P.S. In case you're really interested, Think C crashes when I try to bring projects up to date at the point where it tries to comile MacTraps. The STRANGE thing is that if I turn all of the inits off, reboot, turn them all on again, then reboot again, the problem seems to go away... any clues? I just bought the program, so I haven't isolated the problem yet. I am running 6.0.4 on a vanilla Mac II, tons of inits, 5 megs RAM. 100 meg HD, MacSprint board.
jtn@potomac.ads.com (John T. Nelson) (08/25/90)
> Is there a list somewhere of the init that THINK C 4.0 has problems > with? I am experiencing some weird stuff that I think must be init > problems... > Thomas Summerall I seem to be having problems with void ** and the stack. A friend has problems with void * which are similar. Here's some example code: unsigned long symbol; char *word; functionA(word, &symbol) } functionA(char *w, unsigned long *symbol) { functionB(&symbol); /* value of symbol is garbage */ } functionB(void **symbol) { unsigned long *s; *s = 5; memmove(*symbol, s, sizeof(unsigned long)); } Something like the above. When we get to the above comment, the value of symbol is garbage. Strange thing is that this isn't ALWAYS true. Sometimes it works, sometimes it doesn't. Most times it does. Clearly there's a problem with the void ** or void * type. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ORGANIZATION: Advanced Decision Systems GEOGRAPHIC: Arlington, VA UUCP: kzin!speaker@mimsy.umd.edu INTERNET: jtn@potomac.ads.com SPOKEN: Yo... John! PHONE: (703) 243-1611 PROJECT: The Conrail Locomotive/Harpsichord Fusion Program =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=