Debugging leaves

Comments

I think the following way looks more simple and also is a bit more correct:

#define __LEAVE_IF_ERR(_c) ((_c >= 0) || (({__BREAKPOINT(); User::Leave(_c);}), 0))

The __BREAKPOINT macro is defined in e32def.h.

ivey

Purely out of curiosity: what do these assembly statements do? On Windows and on the target platform. Thanks!

tote_b5

to Tote: int 3 - is the breakpoint.

to Ivey: In you proposal statement _c is executed two times if leave occurs. If you wrap Int32 SomeFunction() to macro then the function would be called twice.

alones 14:01, 21 August 2007 (UTC)

Well, I already know that __BREAKPOINT is indeed an int 3. But I still don't know what this interrupt does in practice? On Windows. And what about the target platform? Thanks!

tote_b5

Thanks for the comment, Alones! I have really missed it.

ivey

Log in or Join to leave comments.

Article Metadata

---

Article

Translated:

From Отладка_сброса_(leave)

By alones

Last edited: hamishwillee (19 Oct 2011)

Original (Russian): Отладка сброса (leave)

---

Debugging Leave situations might be tedious. It would be much easier if the debugger could catch leaves and break the code execution. Luckily, there is a way to achieve it:

#define __LEAVE_IF_ERR(_c) TInt32 __reason = _c;       \
                           if (__reason < 0) {         \
                              __BREAKPOINT();          \
                              User::Leave(__reason);   \
	                   }

The usage of this macro is similar to using User::LeaveIfError(), e.g. __LEAVE_IF_ERR(iFs.Connect()).