http://bugs.winehq.org/show_bug.cgi?id=8936
--- Comment #24 from Konstantin Svist fry.kun@gmail.com 2007-12-22 02:04:31 --- (In reply to comment #23)
Thanks for finding the problem!
We need:
wintab_internal.h: // comment explaining the meaning of this value ... // (159 chars + 2 fuzzy brackets + 1 endline) #define MAX_DUMPBITS_LENGTH 162
tests/context.c: A test function that fills a buffer of size MAX_DUMPBITS_LENGTH with '\0' and then calls DUMPBITS(0xFFFFFFFF, buf). I'm not a C specialist myself, it would be nice to calculate dynamically 0xFFFFFFFF in case sizeof(int) varies. The actual test would be to check that buf[MAX_DUMPBITS_LENGTH - 2] == '}' && buf[MAX_DUMPBITS_LENGTH - 1] == '\0' If you need help setting up the tests directory, tell me when you get stuck, I will try to help.
context.c: Use the new define instead of "200". Regarding DUMPCONTEXT, it should be refactored to get rid of the "4000" value, but that should be a different patch.
What do you think?
Well, if it were up to me, I'd much rather use a language that manages memory for me.. (D, for example) :) Just noticed an example posted at http://winehq.org/site/docs/winedev-guide/dbg-notes. Is that one safe to use?