<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Olaf, this is a bug and should be fixed.<BR>Like someone calling abort or assert(false) or NtRaiseHardError or dereferencing NULL or such.<BR>Or skip those tests on NT386 for now.<BR>And please provide an easy way to run specific tests.<BR>I'm working on adding some tests (ok, just one) and it seems to be a pain.<BR>I think it's just cm3 -FA ../../TESTARGS but it wasn't working.<BR>
<BR>Install the debuggers:<BR>
<BR> <A href="http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx">http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx</A> <BR>
<BR>
I install to c:\bin\x86 and c:\bin\amd64, though the default is c:\program files\blah. <BR> mkdir c:\symbols this is just for a local cache, not needed but nice <BR>
<BR>
cd <somewhere> <BR>
c:\bin\x86\windbg -o -G -g -y srv*c:\symbols*http://msdl.microsoft.com/download/symbols cm3 <BR>
<BR>
When there is a popup, type:<BR>
<BR>
~*k <BR>
<BR>to get all the thread stacks, and see which one is in MessageBox or abort or whatnot.<BR>
<BR>And send the stack? Or all of them if uncertain.<BR>
You can also make a full or minidump with .dump for someone else to look at.<BR>
Good to have the cm3.exe and cm3.pdb as well.<BR>
<BR>Or I guess I can/should just fix them.<BR>I think I've seen a few of these myself.<BR>
<BR>
The stack might not be well displayed by the debugger.<BR>
It could be this in the toplevel exception handler/watson thingy.<BR>
<BR>
Another thing to try is:<BR>
c:\bin\x86\windbg -I<BR>
<BR>
to install windbg as the JIT debugger. That way, some crashes will bring up a debugger, possibly prompting first.<BR>
<BR>
I need to make a web page with a Win32 debugging primer at some point.<BR>
Anyway, I'll try to bump this up in priority.<BR>
<BR>
Could be that SetErrorMode(something) quashes them, but that doesn't mean it isn't a bug.<BR>
Another very good theory is that the "app type", console vs. gui, is relevant.<BR>
Console apps upon abort() or assert(false) print something to stdout/stderr and then exit, whereas gui apps<BR>
use MessageBox. The type is determined from the .exe, and you can change it at runtime via a call.<BR>
<BR>
Not clear to me which of the various catastrophic errors this is though. I think abort().<BR>
<BR> - Jay<BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Mon, 28 Apr 2008 18:42:17 +0200<BR>> From: wagner@elegosoft.com<BR>> To: jayk123@hotmail.com<BR>> CC: m3devel@elegosoft.com<BR>> Subject: Popup Windows stalling regression tests on WinXP<BR>> <BR>> Hi Jay,<BR>> <BR>> everytime I have a look why the regression tests haven't terminated<BR>> yet, I find another popup window with a message like this:<BR>> <BR>> cm3.exe has encountered a problem and needs to close.<BR>> We are sorry for the inconvenience.<BR>> <BR>> Any idea how to suppress this kind of error notification?<BR>> We'll never get reliable regression testing with popup windows :-/<BR>> <BR>> Olaf<BR>> -- <BR>> Olaf Wagner -- elego Software Solutions GmbH<BR>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<BR>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<BR>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<BR>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<BR>> <BR><BR></body>
</html>