- 07 Jul, 2008 40 commits
-
-
Adam Petaccia authored
-
Adam Petaccia authored
-
Adam Petaccia authored
-
Adam Petaccia authored
-
Jeff Smith authored
-
Jeff Smith authored
-
Jon Griffiths authored
-
Jon Griffiths authored
-
Jon Griffiths authored
-
Jon Griffiths authored
-
Jon Griffiths authored
-
Jon Griffiths authored
-
Alexander Morozov authored
-
Alexander Morozov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Nikolay Sivov authored
-
Dylan Smith authored
The error was a memory access of a freed object. In ME_AddUndoItem I checked the top of the undo stack to end a coalescing undo transaction, assuming that this should be either a valid undo item, or NULL, instead it was already freed.
-
Dylan Smith authored
-
Dylan Smith authored
-
Stefan Dösinger authored
Constant numbers start at 0, and the loading loop has a for(i; i < dirtyconsts; i++). This means that the highest dirty constant isn't loaded correctly. Rather than replacing the < with <=, which would make it impossible to have no dirty constant, add 1 to the dirty constant counter.
-
Alexander Nicolaysen Sørnes authored
-
Alexander Nicolaysen Sørnes authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Andrew Talbot authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Alexandre Julliard authored
-
Rob Shearman authored
rpcrt4: Clear the memory of embedded complex types in ComplexUnmarshall when fMustAlloc is TRUE to avoid passing uninitialised memory to the unmarshaller. Found by Valgrind.
-
Vitaliy Margolen authored
Programs looking for this flag to verify if FF is present. And on which axes.
-
Vitaliy Margolen authored
-
Vitaliy Margolen authored
-
Vitaliy Margolen authored
-
Vitaliy Margolen authored
-