16:46:21slyrusso I have a rather annoying memory corruption (or other crash) that only seems to happen when running inside a docker container
16:47:16slyrusit's relatively reproducible and I can get an SLDB prompt when it crashes, but I'm somewhat a loss to use the debugging tools to actually figure out _why_ things go south
16:47:39pkhuong_slyrus: can you try and uncontainerise as many things as possible?
16:48:24slyrusYes, uncontainerizing the SBCL process seems to make the problem go away
16:48:27pkhuong_also is sbcl running as pid 1 in the container?
16:49:16slyrusthe error is usually of the form "Unahndled memory fault at #xD."
16:50:09pkhuong_you can opt out of containerisation for features at a time, this isn't a VM, it's a process + special sauce. if you can figure out what subset of the special sauce causes the crash, finding the problem might be easier.
18:00:35flip214slyrus: I remember having seen strange issues with SBCL within LXR; perhaps there is a connection.
18:01:08flip214please take a look at the ulimits for processes in the container, and/or cgroups settings... pasting them somewhere might help diagnose the problem.