Crash in CPreviewDC::ComputeDeltas as a result of calling TabbedTextOut

[Anthony Wieser]

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=254738

Has anyone got a workaround for this one? It seems it's fixed in the "next
version of Visual Studio".
A lot of good that does me when I'm shipping now, and don't intend to
upgrade to Orcas just yet (if ever).

Apparently, the bug was introduced in VS2005 SP1.

Does anyone have the source of CPrintPreview::TabbedTextOut from the working
release so I can hack it back into my code?

Anthony Wieser
Wieser Software Ltd

[Anthony Wieser]

I've posted a workaround here, but am a bit concerned about the different
kinds of entries in the virtual function tables.
> http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=254738

Does anyone know a place where I can get a comprehensive list of what's
implemented in the vtable for a given virtual funciton?

In the debug build it seems to be this:
tmp.TTO 0x004569d6 [thunk]:CPreviewDC::`vcall'{108,{flat}}' }' CSize (int,
int, const char *, int, int, int *, int)*

// code bytes look like this:
// 004569D6 E9 05 64 02 00 jmp CPreviewDC::`vcall'{108}'
(47CDE0h)

But in the release build it points straight at this:
tmp.TTO 0x0047cde0 CPreviewDC::`vcall'{108}' CSize (int, int, const char
*, int, int, int *, int)*

// code bytes look like this:
// 0047CDE0 8B 01 mov eax,dword ptr [ecx]
// 0047CDE2 FF 60 6C jmp dword ptr [eax+6Ch]

Anything else that might show up here with different compiler options?

Also, does anyone know how the debugger actually generates these types as
shown in tmp.TTO?