Custom Query (301 matches)
Results (49 - 51 of 301)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #199 | fixed | Piping lage amounts of data from/to a child process fails | ||
| Description |
Something seems to be broking with the QIODevice interface to QProcess. This shows up, when the amount of data passed through the pipe is relatively large (100KB+). In "debug" configuration, the program exits with the following message: ASSERT: "pipeData[InPipe].bytesLeft >= written" in file io\qprocess_os2.cpp, line 1390 In "release" configuration, some data is lost. Piping in the opposite direction is unreliable as well. |
|||
| #206 | fixed | QLibrary::load() may give invalid error string | ||
| Description |
When loading a DLL fails because a dependent module of the requested one is missing, QLibray::errorString() is wrong. The reason for that is, that in this case DosLoadModule? returns ERROR_FILE_NOT_FOUND. QLibraryPivate::load_sys() then appends ".DLL" and retries the load. It should not do that, if the failing module is different from the one that was attempted to load. |
|||
| #207 | invalid | omit linking produces make error | ||
| Description |
qmake supports the a CONFIG option named "no_link". It is mostly used when build documentations or other non-source code parts of a program. When that option is present in a *.pro file, qmake generates: LINK = @: IGNORE THIS LINE LFLAGS = -Zomf -Zstack 0x2000 .... When running make, it complains that the program ":" does not exist. |
|||
