Game Development Community

Printf stalling

by Richard_H · in Torque Game Engine · 02/27/2007 (7:13 pm) · 8 replies

It seems that I very innocent looking line has caused my program to come to a halt. No error, it merely seems to freeze up, as if in an infinite loop.
I've traced the culprit down to this line:
Con::printf("Beginning to populate [%d][%d] sized mission.", maxX, maxY);
Both maxX and maxY are S16s and when I debugged they had the value 3.
Does anyone know what error I am making?

Note: I can include more code if this isn't enough.
Edit: Can someone please move this to the private forums?
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine


Torque 3D Owner Tony Richards
#1
02/27/2007 (8:11 pm)
%d is for a 32 bit number and not a 16 bit number, although it shouldn't have caused a crash...

Also, since this is C++, you'd be better off posting in the private forums.

Torque Owner Richard_H
#2
02/28/2007 (3:23 am)
It seems that further debugging revealed it's merely not printing input and the program is stalling later. I tried changing the %d 's to %ld 's or %hd 's, but it still refuses to print.

Torque 3D Owner Tony Richards
#3
02/28/2007 (6:44 am)
First... where do you expect it to print? If you want it to go to a log file then you must have the log file opened.

Torque 3D Owner Pat Wilson
#4
02/28/2007 (10:49 am)
Are you running this from a different thread? The engine uses Con::printf *everywhere*, it is entirely possible that, somehow, there is a deadlock going on.

Torque Owner Richard_H
#5
02/28/2007 (2:18 pm)
I believe I have solved my problem, It seems that I messed it up after changing some seemingly unrelated code. The problem was at first it worked fine, but after other changes printf stopped working and refused to start again. Other printf statements would work fine, but this one statement continued to cause issues. Finally, after fixing up my code it works again, but it seems to have a lag to it. I used my debugger and only several statements later did the line appear in my log file, but at least it works.

Associate Orion Elenzil
Real Life Plus
#6
02/28/2007 (3:17 pm)
Quote:I used my debugger and only several statements later did the line appear in my log file, but at least it works

i believe that's normal - the console.log is buffered.

Torque Owner Stefan Lundmark
#7
02/28/2007 (4:08 pm)
Sounds to me like you tried to access an invalid address (maxX/Y?).

I have never seen any lag though.

Torque Owner Richard_H
#8
02/28/2007 (4:16 pm)
Quote:... when I debugged they had the value 3
I checked the value of both variables.