Perhaps you could run your program in debugger mode and set a breakpoint in the routine that prints the error message? (I'm assuming the error comes from somewhere in the insides of error or warning, but I've never done any spelunking there, so I have no hints for you there....)