From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: 2.6.12-rc1 breaks dosemu Date: Sat, 26 Mar 2005 14:49:44 +0100 Message-ID: <200503261449.46219.arnd@arndb.de> References: <20050320021141.GA4449@stusta.de> <1111824629.6293.19.camel@laptopd505.fenrus.org> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE In-Reply-To: Content-Disposition: inline Sender: linux-msdos-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="utf-8" To: Bart Oldeman Cc: Arjan van de Ven , Adrian Bunk , linux-kernel@vger.kernel.org, linux-msdos@vger.kernel.org, Ingo Molnar On S=C3=BCnnavend 26 M=C3=A4rz 2005 09:18, Bart Oldeman wrote: > On Sat, 26 Mar 2005, Arjan van de Ven wrote: >=20 > > > eip: 0x000069ee esp: 0xbfdbffcc eflags: 0x00010246 > > > > hmm interesting. Can you check if at the time of the crash, the esp= is > > actually inside the stack vma? If it's not, I wonder what dosemu do= es to > > get its stack pointer outside the vma... (and on which side of the = vma > > it is) The esp value is always slightly below the stack vma and above ld.so. Running it a few times gives=20 stack VMA crash esp bfc8f000-bfca4000 bfc5ffcc =20 bffa0000-bffb7000 bff5ffcc =20 bfe0c000-bfe23000 bfdbffcc =20 bf7ff000-bf814000 bf7bffcc =20 bfaa9000-bfabe000 bfa5ffcc =20 bfaa9000-bfabe000 bfa5ffcc =20 bffc5000-bffda000 bff7ffcc =20 bfba9000-bfbbf000 bfb5ffcc =20 bf865000-bf87b000 bf81ffcc =20 bfe7d000-bfe92000 bfe3ffcc =2E.. =20 bff9f000-bffb4000 bff5ffcc =20 bfc73000-bfc89000 bfc3ffcc bffe3000-bfff8000 -> works > To Arnd: >=20 > Another thing you should probably do is to build dosemu with debug > information, and then look into ~/.dosemu/boot.log after it crashes. > That will give you the contents of /proc/self/maps, a gdb backtrace a= nd > various other goodies. >=20 > I've checked it myself but can't reproduce, neither with plain dosemu > 1.2.2 nor with current CVS. I'm using the dosemu-1.2.1-3 binary that currently comes with debian sarge, and would prefer not having to build a new dosemu. As far as I can tell, the command.com that is started belongs to freedos, not comcom. The crash however does happen shortly after the command.com file is opened. Arnd <>< - To unsubscribe from this list: send the line "unsubscribe linux-msdos" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html