Ticket #11184 (closed enhancement: fixed)
Trap directly in the function where wxASSERT is
|Reported by:||faustus||Owned by:|
|Keywords:||assert debug trap||Cc:|
I changed the behavior of wxASSERT_MSG
in order to have the debugger exaclty on the caller macro and not inside
the calling stack of assert functions and dialogs.
Mainly i made all return type of "wxOnAssert" from void to int
to allow the debugbreak macro to be inplace.
I only tested this on msw and also i'm not sure if the place where i put the macro is right.