From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jody Bruchon Subject: ELKS doesn't seem to like large executables Date: Fri, 09 Mar 2012 02:44:12 -0500 Message-ID: <4F59B4CC.10301@jodybruchon.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Sender: linux-8086-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: linux-8086@vger.kernel.org I haven't pinned the cause, but in working on the "BusyELKS" utilities, I have created programs that are over 64K in total size, with segments below 64K in size (as required by ld86). However, upon experimenting with replacing "init" with a link to /bin/busyelks1 (which of course contains "init") the system will boot up to the point that it tries to load init, then just plain dies. Upon turning on some debugging messages, I saw that it effectively crashes the system because it not only fails to start init, it also kills "PID 0" which is supposedly the ELKS process scheduler. Just to be clear, these programs work using the native "elksemu" program on my Linux-i386 system. I can only assume there's a nasty bug in how ELKS loads executables. Anyone have a clue what might be going on? Jody Bruchon