public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Frantisek Hanzlik <franta@hanzlici.cz>
To: solarflow99 <solarflow99@gmail.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: same distro, svn1999 DOSEMU crashes on some PCs on SEGV, on others run fine
Date: Tue, 14 Dec 2010 11:12:24 +0100	[thread overview]
Message-ID: <4D074308.2060902@hanzlici.cz> (raw)
In-Reply-To: <AANLkTinidCqin5L1NEBaO_DB26CGPqsGJKEG4K3NSME7@mail.gmail.com>

solarflow99 wrote:
> there is an rpm built for Fedora14 in rpmfusion also, I don't know if
> that will help this problem or not, but others use it without problems
> in case your compiled version has some kind of difference.
> 
> Hope this helps..
> 
> 
> On Mon, Dec 13, 2010 at 4:28 PM, Frantisek Hanzlik <franta@hanzlici.cz> wrote:
>> Hello all DOSEMU gurus,
>>
>> I encounter weird problem with DOSEMU when trying run it on Fedora 14 i386 -
>> althougt machines are roughly same (HW: P4+/2-4GB RAM/max 3 years old, SW:
>> Fedora 14 i686 up-to-date), on some (6 of these i tried) PCs dosemu seems work
>> fine, on others (i found 5 pieces) dosemu crashes on SIGSEGV shortly after
>> start, in its initialization phase.
>>
>> All PCs are installed from same RPM package, which I compile on one of this
>> PCs, then dosemu/freedos part is at all PCs same too. On all machines dosemu
>> run in vm86 mode ($_cpu_emu = "off", and vm.mmap_min_addr = 0).
>> I tried built dosemu both with dynamically loaded plugins and without them,
>> dosemu behavior not changed. After i add some debug messages to several dosemu
>> modules, dosemu on those five machines crashes in slightly different point,
>> and on six remaining machines work still fine.
>>
>> Unfortunately I'm not C programmer and have no idea how debug and solve this
>> problem. For me this appear as dosemu somewhere before overwrite part its
>> memory. Or maybe want some illegal access to pages which was previously locked
>> by mprotect(). But I not know which is right way for solving this issue, know
>> it anyone?
>>
>> When I run dosemu under gdb, on PCs where it crashes i'm getting this output
>> (sorry for it's length):
>> ...

Hello solarflow99,

thank You for reference at Your build. It would be best when dosemu has been
available directly in Fedora main repo. Or at least regularly in rpmfusion.

I solved this problem (with help in our national Linux forum) - there is
probably some fault in Linux glibc/dynamic loader (ld.so), which isn't capable
resolve references. (Fedora 14 has still glibc with suspicious version
2.12.90, to full-2.13 probably something is absent).

Problem can be now temporarily solved by using:

1) "LD_BIND_NOW=y dosemu"	# LD_BIND_NOW value doesn't matter, should be defined

2) linking dosemu with option "-Wl,-z now"

  reply	other threads:[~2010-12-14 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 21:28 same distro, svn1999 DOSEMU crashes on some PCs on SEGV, on others run fine Frantisek Hanzlik
2010-12-14  7:49 ` solarflow99
2010-12-14 10:12   ` Frantisek Hanzlik [this message]
2010-12-14 14:00     ` solarflow99
2010-12-14 15:14       ` Frantisek Hanzlik
2010-12-14 16:12         ` solarflow99

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=4D074308.2060902@hanzlici.cz \
    --to=franta@hanzlici.cz \
    --cc=linux-msdos@vger.kernel.org \
    --cc=solarflow99@gmail.com \
    /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