Wikipedia's entry for GPL has a good explanation for this matter: http://en.wikipedia.org/wiki/GNU_General_Public_License#Communicating_and_bundling_with_non-GPL_programs
Especially the parts: "The mere act of communicating with other programs does not, by itself, require all software to be GPL; nor does distributing GPL software with non-GPL software. However, minor conditions must be followed that ensures the rights of GPL software is not restricted."
and:
"By contrast, pipes, sockets and command-line arguments are communication mechanisms normally used between two separate programs. So when they are used for communication, the modules normally are separate programs. But if the semantics of the communication are intimate enough, exchanging complex internal data structures, that too could be a basis to consider the two parts as combined into a larger program."
Software licenses, including the GPL, unfortunately cannot give a solid, 100% proof answer in all cases, so it is up to the programmer to try to figure out what the end result is. IANAL, but I think you might be safe, but this is just my opinion and you can't rely on that!
Edit: An additional link: http://ifross.org/en/program-forks-gpl-licensed-program-system-or-vice-versa-call-derivative-work IFROSS is according to itself "Institute for Legal Questions on Free and Open Source Software" and the explanation there is pretty good, and it says you're clear... maybe.