On Mon, Sep 25, 2017 at 07:31:11PM +0200, Jens Reyer wrote:
> >> Yes I read this, an NMU is welcome. I would also be happy if
> >> there would be a new maintainer for dosbox because I use it very
> >> rarely these days and have not much time to take care of the
> >> package.
> >
> > Hey, thanks
On 09/25/2017 05:32 PM, Alberto Garcia wrote:
> On Mon, Sep 25, 2017 at 05:14:21PM +0200, Jan Dittberner wrote:
>
>>> I can handle the NMU if the maintainer (Jan Dittberner) is busy /
>>> unavailable. Jan, are you reading this?
>>
>> Yes I read this, an NMU is welcome. I would also be happy if
On Mon, Sep 25, 2017 at 11:14:17AM +0300, Alberto Garcia wrote:
> On Mon, Sep 25, 2017 at 10:26:05AM +0300, Alberto Garcia wrote:
> > Anyway, this has been fixed upstream a while ago already so we should
> > simply backport the solution. It's a problem in the 64bit dynamic
> > recompiler and the
On Mon, Sep 25, 2017 at 05:14:21PM +0200, Jan Dittberner wrote:
> > I can handle the NMU if the maintainer (Jan Dittberner) is busy /
> > unavailable. Jan, are you reading this?
>
> Yes I read this, an NMU is welcome. I would also be happy if there
> would be a new maintainer for dosbox because
On Mon, Sep 25, 2017 at 10:26:05AM +0300, Alberto Garcia wrote:
> Anyway, this has been fixed upstream a while ago already so we should
> simply backport the solution. It's a problem in the 64bit dynamic
> recompiler and the fix is in r3951:
>
>https://sourceforge.net/p/dosbox/code-0/3951/
>
Control: tags 857341 patch upstream fixed-upstream
Hi,
I had a bit of time to take a look at this. Altough people are
reporting that the dosbox package in jessie (0.74-4) doesn't have
this problem, what happens is not that later versions introduced a
regression, but it rather seems that the bug
Hello. This also appears in unstable.
Downgrading dosbox to jessie's version 0.74-4 resolves the issue.
Linux version 4.9.0-3-amd64
AMD Phenom(tm) II X4 965 Processor
Hi,
happened also here.
Unfortunately, Dosbox is almost unusable without core=dynamic.
Debian Stretch
Kernel 4.9.0-3-amd64
Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
Thanks
Simon
I also had this issue, changing the core= setting did not
help, recompiling the package with --disable-dynamic-core
did.
The attached patch changes the build options accordingly.
--
Stefan Ott
http://www.ott.net/
Index: dosbox-0.74/debian/rules
Package: dosbox
Followup-For: Bug #857341
I'm seeing this as well since dosbox was upgraded from 0.74-4+b1 to
0.74-4.2+b2. Downgrading the package via snapshot.debian.org to 0.74-4+b1 was a
viable workaround for me, and enabled me to use the dynamic/auto core again.
Greets,
Samuel
Infos about
I'm seeing this too. Two days ago dosbox was upgraded from 0.74-4.2+b1
to 0.74-4.2+b2. I don't know what has changed in the new version, but
everything used to work fine before the upgrade. This is in Debian
testing, kernel 4.9.0-2-amd64, running on a Core i5-6400.
I'll also point out that using
Package: dosbox
Version: 0.74-4.2+b2
Severity: normal
Hi,
DOSBox crashes when the emulated CPU is running in dynamic mode with
the following error message:
Exit to error: DRC64:Unhandled memory reference
This can be easily reproduce by setting core=dynamic in the config
file (then DOSBox
12 matches
Mail list logo
