|
![](/i/fill.gif) |
Warp wrote:
> Invisible <voi### [at] dev null> wrote:
>> Hey Warp, what does it mean when you call printf() and the compiler says
>> "suspicious pointer conversion"?
>
> Difficult to say without seeing the actual code.
OK, well obviously 10 years later I don't still have it. All I can
remember is that *loads* of people used to get this error. And it always
seemed to involve printf().
I also remember that several people found that when you run their
compiled program, it dumps many, many pages of gibberish to the console,
and beeps repeatedly, until [if you're lucky] it would randomly stop.
Presumably this is because you gave printf() an int when it was
expecting a char*, and it's now printing out the contents of the
machine's RAM until it happens upon a zero octet... (The deeps are due
to the 0x07 BEL characters.)
I presume this doesn't work on a protected-mode OS?
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |