https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69650
--- Comment #45 from Roger Orr <rogero at howzatt dot demon.co.uk> --- While investigating the problem I am experiencing I have found it is stable across g++ builds - I have tried a build using revision 234741 which has the identical diagnostic output from the compilation. However, small changes to the source code -- such as changing the length of the directory paths involved -- can change whether or not the diagnostic is produced. In the example I posted, if I change path "/home/rorr/linuxdev109ws_9119/..." to "/home/rorr/..." in the line directives of the ii file the compilation succeeds without problem. Hence it is not clear to me whether this diagnostic is the root problem or merely a symptom of a different problem - possibly a memory overwrite or use of an uninitialised variable whose value depends on the history of the memory location.
