Man...this is annoying

[DarylD]

Yes, thats what I have started to do...in fact I have just made an interesting discovery, look at the image I have attached. You will see that the info written to the video buffer seems to have inexplicably been written into a separate area of memory used for object paths. Looks like I may have found my bug

Daryl.

[attachment deleted by admin]

[DarylD]

Hmm...I have beating myself ritually for the last hour with a big stick for missing this one.

In my KPrint routine I had something like this (approximately, this is simplified):

Code: Select all

char buffer[1000];

vsnprintf(buffer, 1000, "%s", string);

Instead of:

Code: Select all

char buffer[1000];

vsnprintf((char *)&buffer, 1000, "%s", string);

To be honest, its a miracle it ever worked!! Unfortunately now, I have other problems due to other bugs being masked by this strange behaviour. I can only assume it ever worked is due to the code generated by the compiler.

So I now have different but just as annoying behaviour!

Daryl.