<div dir="ltr"><div dir="ltr"><div dir="ltr">Hello, <br></div><div dir="ltr"><br></div><div dir="ltr">after some further investigations, it seems that up to now, all core dumps seem to have the same reason. or at least the same smalltalk backtrace: <br></div><div dir="ltr"><br></div><div dir="ltr"><span style="font-family:monospace">C stack backtrace & registers:<br>don't know how to derive register state from a ucontext_t on this platform<br>*0x0 <???> at ???<br>0x25c04a <reportStackState+0xda> at /usr/home/edwin/Smalltalk53/</span><span style="font-family:monospace">opensmalltalk-vm/building/</span><span style="font-family:monospace">linux64x64/squeak.cog.spur/</span><span style="font-family:monospace">build/squeak<br>0x25e237 <sigsegv+0x137> at /usr/home/edwin/Smalltalk53/</span><span style="font-family:monospace">opensmalltalk-vm/building/</span><span style="font-family:monospace">linux64x64/squeak.cog.spur/</span><span style="font-family:monospace">build/squeak<br>0x800414c6e <_pthread_sigmask+0x53e> at /lib/libthr.so.3<br>0x0 <???> at ???<br><br><br>Smalltalk stack dump:<br>0x7ffffffe6608 I [] in DelayWaitTimeout>wait 0x80183ad60: a(n) DelayWaitTimeout<br>0x7ffffffe6648 M BlockClosure>ensure: 0x80183ae50: a(n) BlockClosure<br>0x7ffffffe6690 I DelayWaitTimeout>wait 0x80183ad60: a(n) DelayWaitTimeout<br>0x7ffffffe66d8 I Semaphore>waitTimeoutMSecs: 0x801839db8: a(n) Semaphore<br>0x7ffffffe6720 M [] in SemaphoreTest></span><span style="font-family:monospace">testWaitAndWaitTimeoutTogether 0x801674298: a(n) SemaphoreTest<br>0x7ffffffe6760 I [] in BlockClosure>newProcess 0x80183a380: a(n) BlockClosure</span></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div>A backtrace in the Squeak core dump gives the following result: <br></div><div dir="ltr"><span style="font-family:monospace"><br></span></div><div dir="ltr"><span style="font-family:monospace">* thread #1, name = 'squeak', stop reason = signal SIGABRT<br> * frame #0: 0x000000080062169a libc.so.7`__sys_thr_kill + 10<br> frame #1: 0x000000080061faf4 libc.so.7`__raise + 52<br> frame #2: 0x0000000800595719 libc.so.7`abort + 73<br> frame #3: 0x000000000025e14d squeak`sigsegv(sig=8778880, info=<unavailable>, uap=0x00007ffffff98c40) at sqUnixMain.c:1145:2<br> frame #4: 0x0000000800414c6e libthr.so.3`___lldb_unnamed_</span><span style="font-family:monospace">symbol101$$libthr.so.3 + 222<br> frame #5: 0x000000080041422f libthr.so.3`___lldb_unnamed_</span><span style="font-family:monospace">symbol82$$libthr.so.3 + 319<br> frame #6: 0x00007ffffffff193<br> frame #7: 0x000000000029a7be squeak`interpret [inlined] enterSmalltalkExecutiveImpleme</span><span style="font-family:monospace">ntation at gcc3x-cointerp.c:16517:2<br> frame #8: 0x000000000029a793 squeak`interpret at gcc3x-cointerp.c:2843<br> frame #9: 0x000000000025e031 squeak`main(argc=<unavailable></span><span style="font-family:monospace">, argv=<unavailable>, envp=<unavailable>) at sqUnixMain.c:2175:5<br> frame #10: 0x000000000025aeb0 squeak`_start(ap=<unavailable></span><span style="font-family:monospace">, cleanup=<unavailable>) at crt1.c:76:7<br> thread #2, name = 'squeak', stop reason = signal SIGABRT<br> frame #0: 0x00000008005b561a libc.so.7`__sys_nanosleep + 10<br> frame #1: 0x00000008004119ec libthr.so.3`___lldb_unnamed_</span><span style="font-family:monospace">symbol36$$libthr.so.3 + 44<br> frame #2: 0x00000000003022d9 squeak`beatStateMachine(</span><span style="font-family:monospace">careLess=<unavailable>) at sqUnixHeartbeat.c:361:10<br> frame #3: 0x000000080040f08c libthr.so.3`___lldb_unnamed_</span><span style="font-family:monospace">symbol1$$libthr.so.3 + 348<br>(lldb)</span><div><div dir="ltr"><div dir="ltr">i<br><a> </a></div><div>I suppose if a could set debugging on, the btrace would give some more information, but I don't find how to do this. Probably looking over it somehow.</div><div></div><div>If there are some configurationd options I could change in the mvn script, I don't mind doing some other test, but I don't know enough about C and threads to understand what is going on here. <br></div><div><br></div><div>Mind you, I completely understand that FreeBSD is a smaller OS, and that keeping the VM working on Windiws, Apple an Linux is a dauting task in itself, so no hard feelings if nobody has the time or the motivation to look into this. <br></div><div><br></div><div>I'll probably give it a new try when a new version arrives, one never knows.</div><div><br></div><div>I will be back<br></div><div></div><div><br></div><div>Kind regards <br></div><div><br></div><div>Edwin Ancaer<br></div><div><br></div><div><br></div><div dir="ltr">*<a>;</a></div><div dir="ltr"><br></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op vr 14 jan. 2022 om 13:56 schreef Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" target="_blank">marcel.taeumel@hpi.de</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div id="m_935372980997679079m_8026248546028312898m_-3000183933837918485gmail-m_6498124505647770163__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);text-align:left" dir="ltr">
Hi Edwin --<div><br></div><div>You can find the current list of failing tests in the latest bundle-run here:</div><div><a href="https://github.com/squeak-smalltalk/squeak-app/runs/4811550256?check_suite_focus=true" target="_blank"><span style="font-size:10pt">https://github.com/squeak-smalltalk/squeak-app/runs/4811550256?check_suite_focus=true</span></a><br></div><div><br></div><div>See "Test image of Squeak64-trunk" and there "Run tests". You can kind of ignore failing STON-Tests. But we should fix those, too.</div><div><br></div><div>Best,</div><div>Marcel</div><div></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px">
<p style="color:rgb(170,170,170);margin-top:10px">Am 13.01.2022 10:45:48 schrieb Edwin Ancaer <<a href="mailto:eancaer@gmail.com" target="_blank">eancaer@gmail.com</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div dir="ltr"><div dir="ltr"><div>Marcel, <br></div><div><br></div><div>thanks. I removed the test. on my side <br></div><div><br></div><div>A first question, does it make sense to try to run all the tests after compiling a new version of the VM? <br></div><div>It is of no use spamming the list if some known tests have issues. If such tests exist, is there a list available.</div><div><br></div><div>If it should be of interest, after removing #testOutOfMemory, I have a core dump, seemingly during the execution of #testUnwindDebugger. <br></div><div>.I attached the output of the run of the Squeak VM in the attached file abend.txt, <br></div><div><br></div><div><br></div><div>Some more info about the OS: <br></div><div><span style="font-family:monospace">[edwin@otto</span>pedi ~/Smalltalk53/opensmalltalk-vm]$ uname -a <br>FreeBSD ottopedi 12.3-RELEASE FreeBSD 12.3-RELEASE r371126 GENERIC amd64</div><div><br></div><div>And for squeak itself: <br></div><div></div><div><span style="font-family:monospace">Image<br>-----<br>/usr/home/edwin/Smalltalk53/opensmalltalk-vm/image/Squeak5.3-19431-64bit.image<br>Squeak5.3<br>latest update: #19431<br>Current Change Set: HomeProject<br>Image format 68</span>021 (64 bit)<br><br><span style="font-family:monospace">Virtual Machine<br>---------------</span><br>/usr/home/edwin/Smalltalk53/opensmalltalk-vm/building/linux64x64/squeak.cog.spur/build/squeak<br>Open Smalltalk Cog[Spur] VM [CoInterpreterPrimitives VMMaker.oscog-eem.3133]<br>Unix built on Jan 10 2022 21:08:09 Compiler: FreeBSD Clang 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)<br>platform sources revision VM: 202201051952 edwin@ottopedi:/usr/home/edwin/Smalltalk53/opensmalltalk-vm Date: Wed Jan 5 11:52:55 2022 CommitHash: 8141dd272 Plugins: 202201051952 edwin@ottopedi:/usr/home/edwin/Smalltalk53/opensmalltalk-vm<br>CoInterpreter VMMaker.oscog-eem.3133 uuid: 4a7f4038-9285-42ba-b1fd-b5621a072836 Jan 10 2022<br>StackToRegisterMappingCogit VMMaker.oscog-eem.3127 uuid: 4d6dd04c-143e-41c0-90bb-ed55b27ff3f1 Jan 10 2022</div><div><br></div><div>Kind regards</div><div><br></div><div>Edwin Ancaer<br></div><div><br></div><div><div><div dir="ltr"><div dir="ltr"><a> </a>*<a>;</a><br></div></div></div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op wo 12 jan. 2022 om 14:45 schreef Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" target="_blank">marcel.taeumel@hpi.de</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div id="m_935372980997679079m_8026248546028312898m_-3000183933837918485gmail-m_6498124505647770163gmail-m_-785841128127448680__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0);text-align:left" dir="ltr">
Hi Edwin --<div><br></div><div>> <span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">It looks this happened during the execution of testOutOfMemorySignal.</span></div><div><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">We should really disable this test in its current form ... it has issues on all platforms.</span></div><div><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">Best,</span></div><div><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">Marcel</span></div><div></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px">
<p style="color:rgb(170,170,170);margin-top:10px">Am 10.01.2022 06:31:05 schrieb Edwin Ancaer <<a href="mailto:eancaer@gmail.com" target="_blank">eancaer@gmail.com</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif">
<div dir="ltr"><div>Hello, <br></div><div><br></div><div>Some time ago, begin 2020, I managed to build a Squeak 5.0 VM on FreeBSD, based on the sources in the opensmalltalk-vm github repository.</div><div>I remember having some difficulties, on the way, but everything got solved, and I still have that version working. <br></div><div><br></div><div>Right now, I built linux64x64 Squeak 5.3 cog spur VM on FreeBSD. There were no compilation errors, no linker errors, So I started squeak, started running the tests in TestRunner, and got the following<span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace">[edwin@ottopedi ~/Smalltalk53/opensmalltalk-vm/building/linux64x64/squeak.cog.spur/build]$ ./squeak ../../../../image/Squeak5.3-19431-64bit.image<br>Killed<br>[edwin@ottopedi ~/Smalltalk53/opensmalltalk-vm/building/linux64x64/squeak.cog.spur/build]$ </span></div><div><div><div dir="ltr"><div dir="ltr"><br><a> </a></div><div>It looks this happened during the execution of testOutOfMemorySignal. <br></div><div><br></div><div>Are other people here using Squeak 5.3 on FreeBSD? <br></div><div>Should I still build the linux64x64 version for FreeBSD, and, if so, any idea how to find out what is going wrong?</div><div><br></div><div>Kind regards, <br></div><div><br></div><div>Edwin Ancaer<br></div></div></div></div></div>
</div></blockquote>
</div></div><br>
</blockquote></div>
</div></blockquote>
</div></div><br>
</blockquote></div></div>