***vagrantc_ is now known as vagrantc
<oriansj>CORDIC: it requires a table or a list that is absolutely true but I'd argue that is not an output or input buffer <oriansj>xentrac: you are right about EOF being 4 and not -4; (a little thing I do in my assembly to make it easy to spot copies) <oriansj>pder: excellent job and absolutely right on all those respects <oriansj>latest commit of mescc-tools-seed is now up; mes-m2 with working garbage collection (compaction too) and all working primities on all platforms is now up ***efraim_ is now known as efraim
<fosslinux>oriansj: at this layer of bootstrap is there any way to get debugging symbols in the m2-planet binary or do I need to rely on good old file_print() <janneke>fosslinux: blood-elf can insert function symbols, so that you may get a stack trace <janneke>fosslinux: of course you can use gcc -g and debug that <janneke>if you're so lucky that gcc also segfaults <oriansj>fosslinux: as janneke correctly pointed out blood-elf generates dwarf stubs for all functions; which when combined with M2-Planet's --debug flag, allows for a debuggable binary (see test/test100/hello-amd64.sh for an example of that generation process) <oriansj>The most common issues for segfaults in binaries generated by M2-Planet are around gotos and variable definition inside of loops; also I'd love to see what input causes M2-Planet to segfault ***JenElizabeth96 is now known as jenelizabeth
***ng0_ is now known as ng0
***reepca` is now known as reepca