GPF in DoNotifyWindowAboutCaptureLost()
Kevin Ollivier
kevin-lists at theolliviers.com
Thu May 1 11:11:10 PDT 2008
Hi Neil,
On May 1, 2008, at 10:09 AM, Neil Robinson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Vaclav Slavik wrote:
> | On Thu, 2008-05-01 at 16:07 +0100, Neil Robinson wrote:
> |> At no point do we capture the mouse in any of the code that is
> |> called up to the point where the crash occurs.
> |
> | Clearly, your app does capture the mouse somewhere, otherwise this
> | crash couldn't happen. It may be in some library code, but it does
> | happen, and it would be helpful to know _where_ is the window
> holding
> | capture destroyed.
>
> This is not as easy to establish as you seem to assume. Our code is
> not
> calling any of the capture code. It is also running wx in a completely
> separate thread (since wx requires that it be running things, which is
> something that we can't allow since otherwise our own threads would
> halt).
Wait, are you saying you're not running wx in the application's main
thread? If so, running wx inside a thread is not supported not just by
wx, but by most (all?) of the underlying native toolkits it uses, and
will definitely lead to a lot of strange errors caused by non-
threadsafe code crossing threads. (invalid pointers being a prime
example)
Regards,
Kevin
More information about the wx-users
mailing list