[Date Prev][Date Next][Thread Prev][Thread Next][Thread Index]

RE: [XaraXtreme-dev] Abort on arrow keypress

In fact, we actually do fill with a value, 0xCD.  The real problem here
was the missing line of code in DoWithParam which caused it to try
calling through a pointer set to 0xCDCDCDCD.  Hence the invalid this
pointer mentioned by Martin.

It will definitely need that fixing too before the problem will actually
be resolved.


-----Original Message-----
From: owner-dev@xxxxxxxxxxxxxxxx [mailto:owner-dev@xxxxxxxxxxxxxxxx] On
Behalf Of Alex Bligh
Sent: 28 June 2006 16:37
To: dev@xxxxxxxxxxxxxx
Cc: Alex Bligh
Subject: RE: [XaraXtreme-dev] Abort on arrow keypress

--On 28 June 2006 16:19 +0100 Gerry Iles <GerryI@xxxxxxxx> wrote:

> Looking at the constructor for TransOperation it doesn't actually set
> all of its member variables sensibly.  I've just committed a fix
> that sets the StartSpread and CurrentSpread to NULL so that in release
> builds (when memory isn't auto-nulled on allocation) the test in
> CompleteTransformation works correctly.

/Do/ we auto-null memory on allocation on debug builds? If we are trying
to find bugs, should we not set it some nasty pattern (like we do when
it's deleted)?