Hi all:<br>Olaf, but in the case is not even the cm3 process, but a sub process of it, maybe the linker or/and the assembler (what VS version do you have?) which in turn throws the fault, how do you know from sure is cm3 only causing that?, Can you check the label of "Click here for more information". Then you can click on see the files involved in the fault. There you should see the list of files like dll or lib and executable involved, can you send that info?<br>Thanks<br><br><br><b><i>Olaf Wagner <wagner@elegosoft.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Sorry, I currently have neither the time to install debuggers on my<br>slow VM machine nor to chase after such bugs. What I hoped is that<br>there is some system switch that turns off all such popups.<br>If there is not, there may not be much further progress from me for<br>some time. If I start a program like the compiler
without any GUI<br>from the command line, I do not expect to get any popup boxes on<br>some unmonitored server machine. It will just not work this way.<br><br>Even if I found and fixed this special problem now, we'll run into<br>the next one some time later when the tests are hanging again...<br><br>Olaf<br><br>PS: As for running only one test with the m3tests makefile, I simply<br> switch off most of the definitions with `if "" ... end' and<br> copy the interesting line just before.<br><br>Quoting Jay <jayk123@hotmail.com>:<br><br>> Olaf, this is a bug and should be fixed.Like someone calling abort <br>> or assert(false) or NtRaiseHardError or dereferencing NULL or <br>> such.Or skip those tests on NT386 for now.And please provide an easy <br>> way to run specific tests.I'm working on adding some tests (ok, <br>> just one) and it seems to be a pain.I think it's just cm3 -FA <br>> ../../TESTARGS but it wasn't working.<br>> Install the
debuggers:<br>> http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx<br>><br>> I install to c:\bin\x86 and c:\bin\amd64, though the default is <br>> c:\program files\blah. mkdir c:\symbols this is just for a local <br>> cache, not needed but nice<br>><br>> cd <somewhere><br>> c:\bin\x86\windbg -o -G -g -y <br>> srv*c:\symbols*http://msdl.microsoft.com/download/symbols cm3<br>><br>> When there is a popup, type:<br>><br>> ~*k<br>> to get all the thread stacks, and see which one is in MessageBox or <br>> abort or whatnot.<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>> Or I guess I can/should just fix them.I think I've seen a few of <br>> 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 <br>> 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 <br>> mean it isn't a bug.<br>> Another very good theory is that the "app type", console vs. gui, is <br>> relevant.<br>> Console apps upon abort() or assert(false) print something to <br>> stdout/stderr and then exit, whereas gui apps<br>> use MessageBox. The type is determined from the .exe, and you can <br>> change it at runtime via a call.<br>><br>> Not clear to me which of the various catastrophic errors this is <br>> though. I think
abort().<br>> - Jay<br>><br>><br>><br>>> Date: Mon, 28 Apr 2008 18:42:17 +0200> From: wagner@elegosoft.com> <br>>> To: jayk123@hotmail.com> CC: m3devel@elegosoft.com> Subject: Popup <br>>> Windows stalling regression tests on WinXP> > Hi Jay,> > everytime <br>>> I have a look why the regression tests haven't terminated> yet, I <br>>> find another popup window with a message like this:> > cm3.exe has <br>>> encountered a problem and needs to close.> We are sorry for the <br>>> inconvenience.> > Any idea how to suppress this kind of error <br>>> notification?> We'll never get reliable regression testing with <br>>> popup windows :-/> > Olaf> -- > Olaf Wagner -- elego Software <br>>> Solutions GmbH> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, <br>>> Germany> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869
fax: <br>>> +49 30 23 45 86 95> http://www.elegosoft.com | Geschäftsführer: <br>>> Olaf Wagner | Sitz: Berlin> Handelregister: Amtsgericht <br>>> Charlottenburg HRB 77719 | USt-IdNr: DE163214194><br><br><br><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></somewhere></jayk123@hotmail.com></blockquote><br><p>
<hr size=1><br><font face="Verdana" size="-2">Enviado desde <a href="http://us.rd.yahoo.com/mailuk/taglines/isp/control/*http://us.rd.yahoo.com/evt=52431/*http://es.docs.yahoo.com/mail/overview/index.html">Correo Yahoo!</a><br>La bandeja de entrada más inteligente.<br></font>