Strange output

BlitzMax Forums/BlitzMax Beginners Area/Strange output

Arry(Posted 2008) [#1]
Hi all,

I'm getting some odd output when running up a project of mine. The output in the IDE is

wx=0.345750, wy=0.358550, rx=0.648500, ry=0.330880
gx=0.321210, gy=0.597870, bx=0.155890, by=0.066040
wx=0.345750, wy=0.358550, rx=0.648500, ry=0.330880
gx=0.321210, gy=0.597870, bx=0.155890, by=0.066040
wx=0.345750, wy=0.358550, rx=0.648500, ry=0.330880
gx=0.321210, gy=0.597870, bx=0.155890, by=0.066040

and this goes on and on for the length of time the game loop is running.

I'm not in debug mode, and these are not any of my variable names.

Does anyone know what these figures/letters represent?

Thanks.


Grey Alien(Posted 2008) [#2]
sounds like you've left a Print statement in or maybe you are using someone else's code (or module) and they've left a print statement in?


Arry(Posted 2008) [#3]
Good thinking, but alas no. :-(


Jesse(Posted 2008) [#4]
there is no way anyone can help you if you don't post the code.


tonyg(Posted 2008) [#5]
What level of BlitzMax are you using?
What happens when you search the project folder for 'wx' or 'print'?
What third-party modules are you using?
When did you first notice the output and what had changed?
What happens when you put a debugstop within your loop and then step through?


Arry(Posted 2008) [#6]
OK - this happens on the latest version.
On versions prior I also get :

libpng warning: Ignoring incorrect cHRM value when sRGB is also present

prior to :
wx=0.345750, wy=0.358550, rx=0.648500, ry=0.330880
gx=0.321210, gy=0.597870, bx=0.155890, by=0.066040

...then repeat.

there are no results for wx or print, when I search.
This has been there sometime, it's an old project I've gone back to.

I am not using any 3rd party modules.

I'm not really sure what I'd be looking for with the debugstop, sorry. I've run it and nothing untoward seems to be going on.

@Jesse - I appreciate what you're saying, but there's 3504 lines of code. Since I don't have any ideas whatsoever as to what's causing this I don't know which parts to post up.


Brucey(Posted 2008) [#7]
I would guess it's coming from libpng


tonyg(Posted 2008) [#8]
Add print statements to your code outputting the function or method name being used.
Check between which functions the messages are produced. Concentrate on that area and adding more print statements until you're pretty certain you are close enough to know where to add a debugstop. When stopped press the debugstep button.
Keep checking the background window and check when the wx messages are displayed. Reset the debugstop so it is closer to the error and then use the step-in and check whether it is from another module.


Brucey(Posted 2008) [#9]
No, really, it's probably coming from libpng.


Brucey(Posted 2008) [#10]
pngrutil.c
            fprintf(stderr,"wx=%ld, wy=%ld, rx=%ld, ry=%ld\n",
               int_x_white, int_y_white, int_x_red, int_y_red);
            fprintf(stderr,"gx=%ld, gy=%ld, bx=%ld, by=%ld\n",
               int_x_green, int_y_green, int_x_blue, int_y_blue);



Perturbatio(Posted 2008) [#11]
corrupt png maybe?


Arry(Posted 2008) [#12]
Thanks guys, I have narrowed it down to a couple of dodgy png's.