Correct me if I'm wrong, but I believe the situation you describe is like this:
- You have a GPL or LGPL program, built as a separate executable, with no modifications made by you.
- You are building a closed-source application that needs the functionality of the GPL or LGPL program.
- In your program, you use your framework or OS facilities for running another, separate executable.
- You are using the output of that executable in your program.
If that's the case, you're not actually linking to the GPL- or LGPL-licensed program. Thus, you're not bound by the license terms of that program. This is actually a fairly common, if complicated, way to avoid licensing issues with such executables.
However, it does violate the spirit of the GPL and the LGPL.