21:08:40drmeisterkpoeck: If you want to get a more descriptive backtrace you can do the following. Copy and paste the backtrace you got into a file - say /tmp/backtrace.txt
21:09:43drmeisterWhere <pid> is the pid of the process that generated the backtrace.
21:10:15drmeisterkpoeck: Yes. Any file that contains strings that look like ... 0x000000011a611708
21:10:56drmeistersymbolicate.lisp recognizes those and if they fall in the function address ranges that are in /tmp/perf-<pid>.map - it converts those addresses into jitted symbol names.
21:11:06drmeisterYou can do it with any text file.
21:11:24drmeisterThat's how flame graphs get jitted function names.
21:13:03drmeisterYou need the perf-<pid>.map file that corresponds to the same run that generated the backtrace.
21:13:22drmeisterkpoeck: It's hard to tell from the error and backtrace that you pasted - but at what stage of the build does that error happen?
21:13:39drmeistercclasp is building on linux using the latest master
21:13:55drmeisteraclasp is building on macOS also using the latest master
21:14:05kpoeckI happens the moment asdf should be compiled
21:14:18drmeisterAh - ok - I haven't gotten to that stage in either build.