Someone takes a GIMP plug-in licensed under GPL and converts it to a Photoshop plug-in (which is a DLL and shares memory space with Photoshop).
According to GPL, Photoshop would now have to be open-sourced, but the person, who converted the plug-in does not have access to Photoshop source code.
What now? Goes GPL actually forbids the existence of this? What if the converted plug-in with the source code is published? Is that actually illegal? What if they only publish the adapted source code and not the binary? What if a third person compiles it and publishes the binary? Who would be the guilty party?
(The legal definition of 'derived works' is based in case law and is more complex than what you'd find in a FSF FAQ.)
That would only be true if the distributor failed to provide the source code to any interested party who asked for it. If he met that requirement, and if he included all the original copyright notices in the source along with his own, there's no violation.
This, for example, is why the FSF always mentions explicitly that they do not consider merely using a tool like grep as part of a shell script to be a derived work. They have to be reasonable, or they lose their power.
> 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. - http://www.gnu.org/licenses/gpl-faq.html