Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: printf()
Message-ID: <44110@sun.uucp>
Date: 3 Mar 88 21:44:17 GMT
References: <7364@cisunx.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 22

In article <7364@cisunx.UUCP> ejkst@cisunx.UUCP (Eric J. Kennedy) writes:
>Now, my question is, why the heck didn't my message print out if it was
>before the actual bug?  

Well if the lack of the pointer was the true reason for the bug then I 
can't guess why it wouldn't print out the error. If however you had a
statement like :

	int	foo = somefunc(value);
	    -or a favorite-
	UBYTE	data[47];
	int	datum = *(int *)(&data[3]);
		^- Causes odd address GURU because data[3] is on odd word

in your declarations somewhere then you might have a problem. Look at
the assembly source and find out where it really starts executing the
code. And also to see if anything besides the startup file gets executed
before the compiler. Last but not least make sure you are using the correct
startup code for the compiler/version you are running. 

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.