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

Re: [Xen-devel] debugging frustration

Luciano Miguel Ferreira Rocha wrote:

Yes, but an empty macro results in the same thing as a do {} while (0)
a = b

compiles cleanly if DEBUG is #define'd as ''

At the end of the day, we're dealing with a very imperfect system (cpp). My philosophy on debug() macro's is that they should always map 1-1 to a real function and simply provide that function with __LINE__, __FUNCTION__, and __FILE__.

If you're really concerned about performance, you can #ifdef DEBUG the body of the function and most compilers will correctly do nothing for those calls.

If it's any consolation, the next submission of VM-Tools will have a set of logging functions. I can certainly submit patches to xcs and friends to use these functions..


if (ptr == null)
   *ptr = 2

The only problem is when the macro has some code (AFAIK).

Anthony Liguori

SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.