IRC channel logs

2019-11-04.log

back to list of logs

<xentrac>oriansj: Calculus Vaporis is reported to be considerably less of a bitch to program than it first appears, but perhaps that's damning it with faint praise
<oriansj>xentrac: I was referrring to that FPGA; we have previously discussed the merits of Calculus Vaporis
<xentrac>oh, agreed
<xentrac>hopefully that will improve
<pder>I am not sure if this is an issue, but out of curiosity i tried running mes-m2 through valgrind. It reports the following error and segfaults. Other trivial programs made with M2-Planet don't seem to have this problem.
<pder>==5437== Command: ./mes-m2
<pder>==5437==
<pder>==5437== brk segment overflow in thread #1: can't grow to 0xfe6d000
<pder>==5437== Invalid write of size 1
<pder>==5437== at 0x80483D5: FOR_THEN_memset_0 (in /home/pder/mescc-tools-seed/bin/
<pder>mes-m2)
<pder>==5437== by 0xFEFF450B: ???
<pder>==5437== by 0xFEFF451F: ???
<pder>==5437== by 0xFEFF452B: ???
<pder>==5437== Address 0xffffffff is not stack'd, malloc'd or (recently) free'd
<janneke>pder: running valgrind is a nice idea :)
<vagrantc>oriansj: awesome news regarding mescc-tools-seed!
<pder>Regarding the valgrind failure with mes-m2 that I posted earlier, I found a solution by patching valgrind and rebuilding to increase the brk segment size.
<pder> https://tutel.me/c/programming/questions/35129135/valgrind+reporting+a+segment+overflow
<pder>:q
*janneke prepares a patch!
<janneke>oriansj: hmm, tried to cc you; got jeremiah@pdp10.guru retry timeout exceeded...
<janneke>
<janneke>oriansj: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38063