"Graph" example's use of QResource is dangerous

I've based some materials in a larger application on the use of QSGSimpleMaterialShader in the graph example classes NoisyShader and LineShader.

The example returns the shader source code like this:

    const char *vertexShader() const {
        QResource r(":/scenegraph/graph/shaders/line.vsh");
        Q_ASSERT(r.isValid());
        return (const char *) r.data();
    }

    const char *fragmentShader() const {
        QResource r(":/scenegraph/graph/shaders/line.fsh");
        Q_ASSERT(r.isValid());
        return (const char *) r.data();
    }

However, looking into the actual resource qrc_xxx.cpp file, the data is not null-terminated. So in some cases, especially when a shader file is the last one in the cpp file, the code reading the (const char*) will read beyond until it hits some other null termination. Shader compilation fails, and the application will crash somewhere in the scenegraph render thread.

Seems like this goes well for shader files not being the last in the list, because the header field for the next file is a 4 byte size where the first byte tends to be zero. I'm just guessing.

Another issue is that the data in the resource file could be compressed, but the example code assumes it is not.