'unitTest_RelationalCool_RalSequence.exe': Loaded 'C:\WINNT\system32\advapi32.dll', No symbols loaded. 'unitTest_RelationalCool_RalSequence.exe': Loaded 'C:\WINNT\system32\ws2help.dll', No symbols loaded. 'unitTest_RelationalCool_RalSequence.exe': Loaded 'C:\WINNT\system32\msvcrt.dll', No symbols loaded. 'unitTest_RelationalCool_RalSequence.exe': Loaded 'C:\WINNT\system32\ws2_32.dll', No symbols loaded. 'unitTest_RelationalCool_RalSequence.exe': Loaded 'C:\WINNT\system32\gdi32.dll', No symbols loaded. 'unitTest_RelationalCool_RalSequence.exe': Loaded 'C:\WINNT\system32\user32.dll', No symbols loaded. 'unitTest_RelationalCool_RalSequence.exe': Loaded '\\afs\all\cern.ch\sw\lcg\app\releases\SEAL\SEAL_1_8_1\win32_vc71_dbg\lib\lcg_SealBase.dll', Symbols loaded. This is reproducible enough to be debugged next weekĪttachment screenshot.GIF has been added with description: Screenshot of visual studio error messageĮxecuted the RalSequenceTest from cygwin using the VisualStudio debugger (thanks Marco!!).Īctually nothing starts, its has problems loading the symbols:
I am also leaving for the weekend soon, but I'll have a look next week. It has to be investigated, but I cannot do it now. I do not know who is keeping an handle in python. If the handle was valid when the application was destroyed, I got that assertion. I encountered it when I tried to change cool::Application to return seal::IHandle. Means that one of the services was not deleted before deleting the context. Wine problem in C++ observed again at the same place.ĭo not change the libraries and try to debug this next week?Īssertion failed: `pos != m_children.end ()' (in /afs/cern.ch/sw/lcg/app/releases/SEAL/SEAL_1_8_1/src/Framework/SealKernel/src/Context.cpp:40) Renamed as "Assertion (in a loop) for C++/P圜ool/P圜oolUtilities on Linux/Windows". That means no ROOT involved:Īssertion loop observed on P圜oolUtilities also on Linux: when running in background), I guess it "thinks" that you gave it an answer like "", which it does not understand, so it asks it againg.Īnother assertion loop on Windows, this time in the C++ tests rather than on P圜ool. If the program is disconnected from a terminal (e.g. If you run the test by hand it will print it only once and wait for your reply.
It happend only when you run the tests from the script execUnitTests.sh. Just for the reference, I write here what I told you yesterday about the repetition ofīort, etry, gnore, ore, tack trace? assertion failed: `s_trampolines ' (in. Note that this one also affects P圜ool, e.g. This logfile presents instances of both this bug and bug #18225.įiled this as a separate bug for completeness. Assertion (in a loop) for P圜ool and P圜oolUtilities on Windows.
0 kommentar(er)
