public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Bart Oldeman <bartoldeman@users.sourceforge.net>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Adrian Bunk <bunk@stusta.de>,
	linux-kernel@vger.kernel.org, linux-msdos@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.12-rc1 breaks dosemu
Date: Sat, 26 Mar 2005 14:49:44 +0100	[thread overview]
Message-ID: <200503261449.46219.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0503262009040.3040@enm-bo-lt.localnet>

On Sünnavend 26 März 2005 09:18, Bart Oldeman wrote:
> On Sat, 26 Mar 2005, Arjan van de Ven wrote:
> 
> > > 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 does 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 

stack VMA         crash esp
bfc8f000-bfca4000 bfc5ffcc  
bffa0000-bffb7000 bff5ffcc  
bfe0c000-bfe23000 bfdbffcc  
bf7ff000-bf814000 bf7bffcc  
bfaa9000-bfabe000 bfa5ffcc  
bfaa9000-bfabe000 bfa5ffcc  
bffc5000-bffda000 bff7ffcc  
bfba9000-bfbbf000 bfb5ffcc  
bf865000-bf87b000 bf81ffcc  
bfe7d000-bfe92000 bfe3ffcc
...  
bff9f000-bffb4000 bff5ffcc  
bfc73000-bfc89000 bfc3ffcc
bffe3000-bfff8000 -> works

> To Arnd:
> 
> 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 and
> various other goodies.
> 
> 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 <><

  reply	other threads:[~2005-03-26 13:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20  2:11 2.6.12-rc1 breaks dosemu Adrian Bunk
2005-03-20  3:04 ` Gene Heskett
2005-03-25 18:52 ` Arnd Bergmann
2005-03-25 19:14   ` Arjan van de Ven
2005-03-25 22:54     ` Arnd Bergmann
2005-03-26  8:10       ` Arjan van de Ven
2005-03-26  8:18         ` Bart Oldeman
2005-03-26 13:49           ` Arnd Bergmann [this message]
2005-03-26 14:28             ` Arjan van de Ven
2005-03-26 14:35               ` Arjan van de Ven
2005-03-26  8:25       ` Arjan van de Ven
2005-03-26  8:32         ` Bart Oldeman
2005-03-26  9:28           ` Arjan van de Ven
2005-03-31  6:43             ` Bart Oldeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200503261449.46219.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=arjan@infradead.org \
    --cc=bartoldeman@users.sourceforge.net \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-msdos@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox