Truly bizzare fprintf() problem
Truly bizzare fprintf() problem
- Subject: Truly bizzare fprintf() problem
- From: "Karan, Cem (Civ,ARL/CISD)" <email@hidden>
- Date: Mon, 19 Apr 2004 11:59:16 -0400
- Thread-topic: Truly bizzare fprintf() problem
I'm having a truly bizarre fprintf() problem and want to know if anyone
else has run into it. If not, I'll file a bug report.
I have a program that at one part of it outputs to a file using
fprintf() like this:
fprintf(outFile, "%u\n", foo);
where foo is an unsigned int, and outFile is an open and correct file
descriptor. When I turn off the optimizer completely, then the file has
the correct number printed out. If I turn on any optimization level,
then I get bizzare numbers being written out that make no sense. If I
look at it using the debugger then in both cases the correct number is
being generated for foo (I can see what it is right before it hits the
fprintf()). I'm at a complete loss as to what could be causing this.
Has anyone seen or heard of something this odd before?
Thanks,
Cem Karan
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.