Hi Eric,
After some experimenting along the lines that you suggested (DEBUG_PrintTypeCast faulted!), it may be that the problem is something to do with the 'bool' type as I now eventually get lots of errors like this:
Unknown type '1' failure on _Bool:t(0,21)=@s8;-16; at 16;
Dave
----- Original Message ----- From: "eric pouech" eric.pouech@wanadoo.fr To: "Dave Hawkes" daveh-wine@cadlink.com Cc: wine-devel@winehq.com Sent: Tuesday, November 20, 2001 3:12 PM Subject: Re: winedbg error
Dave Hawkes wrote:
This occurs whenever winedbg attempts to load the symbols from a
particular
large application that I have, either due to a fault or if I start
windbg
directly on the command line. The debug terminal window will start with
the
winedbg starting message appearing and will them immediately terminate
with
this error.
ok, sounds like winedbg is loading MSC debug info and fails... you could remove the assert in types.c (for DEBUG_CopyFieldlist) another quick test would be to print, in DEBUG_CopyFieldlist, the reasons of the failed assertion: if (!(dt->type == dt2->type && ((dt->type == DT_STRUCT) || (dt->type == DT_ENUM)))) { DEBUG_Printf(DBG_CHN_MESG, "Copyfield list mismatch (%d<>%d): ", dt->type, dt2->type); DEBUG_PrintTypeCast(dt); DEBUG_Printf(DBG_CHN_MESG, " "); DEBUG_PrintTypeCast(dt2); DEBUG_Printf(DBG_CHN_MESG, "\n"); } just to see what gives...
--
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle