Re: Seg fault after quitting FoxPro 6 app

Re: Seg fault after quitting FoxPro 6 app

[Stas Sergeev]

Hello.

Oscar A. Valdez wrote:
> A friend reports a segmentation fault after quitting a FoxPro 2.6
> application for the second time.
> Dosemu: 1.0.2.1
Update your dosemu!

Re: Seg fault after quitting FoxPro 6 app

[Oscar A. Valdez]

Isn't 1.0.2.1 the latest 'stable' version, whilst 1.1.3 is unstable' ?

Or does FoxPro 2.6 only run under 1.1.3 ?

Oscar

El jue, 19-09-2002 a las 15:33, Stas Sergeev escribió:
> Hello.
> 
> Oscar A. Valdez wrote:
> > A friend reports a segmentation fault after quitting a FoxPro 2.6
> > application for the second time.
> > Dosemu: 1.0.2.1
> Update your dosemu!
> 
> -
> 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
-- 
Oscar A. Valdez
Gerente de Finanzas y Administración
Plastipak, S.A. de C.V.

-
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

Re: Seg fault after quitting FoxPro 6 app

[Bart Oldeman]

On 19 Sep 2002, Oscar A. Valdez wrote:

> Isn't 1.0.2.1 the latest 'stable' version, whilst 1.1.3 is unstable' ?

Yes. But there are quite a few bugs that were fixed in 1.1.3.x.
Some code 1.1.3.x is relatively untested and that is the difference.

> Or does FoxPro 2.6 only run under 1.1.3 ?

Maybe even only 1.1.3.4. There were quite some FoxPro related bug fixes
recently.

It's basically like this:

if 1.0.2.1 works for you then stick with it.

if it doesn't, well either use 1.1.x and live with its potentially
untested code (don't worry, it works for me and others, but no
guarantees, for instance there was a buffer overflow in 1.1.3.3 that
could cause "random" crashes - hence the warning on dosemu.org), or
don't use DOSEMU at all.

Bart

Re: Seg fault after quitting FoxPro 6 app

[Stas Sergeev]

Hello.

Bart Oldeman wrote:
>> Isn't 1.0.2.1 the latest 'stable' version,
>> whilst 1.1.3 is unstable' ?
>  Yes.
Well, no:)
Consider this: 1.0.2.1 had enough *known* bugs
for too long. Version that have known bugs (in
contrast to unknown, which are always present)
can't be called "stable" or recommended for a
real use IMO, esp. when such bugs are many and
some are serious.

> It's basically like this:
> if 1.0.2.1 works for you then stick with it.
That's true but atleast every person must be aware
that this version have *known* bugs and there is
another version which doesn't have atleast those.
This is what most people not even suspect (but
for the readers of this list it is strange:)

Re: Seg fault after quitting FoxPro 6 app

[Bart Oldeman]

On Fri, 20 Sep 2002, Stas Sergeev wrote:

> Bart Oldeman wrote:
> >> Isn't 1.0.2.1 the latest 'stable' version,
> >> whilst 1.1.3 is unstable' ?
> >  Yes.
> Well, no:)
> Consider this: 1.0.2.1 had enough *known* bugs
> for too long. Version that have known bugs (in
> contrast to unknown, which are always present)
> can't be called "stable" or recommended for a
> real use IMO, esp. when such bugs are many and
> some are serious.

There are no really "release critical" bugs in 1.0.2.1 if you run DOSEMU
non-suid-root. If you run DOSEMU suid-root, yes, but then we strongly
recommend not to do that if your machine is "net-open".

Ideally dosemu 1.0.3 would have been released which fixes those known
bugs. It has not been released yet, so we're stuck with 1.0.2.1.

There are quite a few annoying bugs, agreed - for instance a SIGSEGV if
your xterm is too big, the serial code does not work for normal users,
there are mouse problems with some programs, ...

But there are a lot of things you can do with 1.0.2.1 without being
affected by those bugs.

> > It's basically like this:
> > if 1.0.2.1 works for you then stick with it.
> That's true but atleast every person must be aware
> that this version have *known* bugs and there is
> another version which doesn't have atleast those.
> This is what most people not even suspect (but
> for the readers of this list it is strange:)

Yes - but 1.1.x can have *new* bugs because it contains code that is not
as widely tested, *at any stage*. This is something which should not be
forgotten. 1.1.3.2 may be fairly stable and then 1.1.3.3 can just crash
at any time under normal use (which dosemu 1.0.2.1 does not do).

Bart

Seg fault after quitting FoxPro 6 app

[Oscar A. Valdez]

A friend reports a segmentation fault after quitting a FoxPro 2.6
application for the second time.

Dosemu: 1.0.2.1; Slackware 8.1 (kernel 2.4.18)

Hints and tips will be appreciated.

Oscar Valdez

-----Mensaje reenviado-----

From: Haller Javier Bracho H. <hbracho@linux.org.ve>
To: Oscar A. Valdez <oscar.valdez@plastipak.com.sv>
Subject: Asesoria DOSemu
Date: 19 Sep 2002 14:38:47 +0000

Hola Oscar, vi tu email en la lista de correos del dosemu (espero que hables 
español ! ).

Tengo un pequeño inconveniente con el dosemu. Estoy ejecutando una aplicacion 
hecha en FoxPro 2.6 y cuando saldo de la aplicación por segunda vez el dosemu 
hace crash. Estoy usando el dosemu 1.0.2.1 bajo Slackware 8.1 (kernel 2.4.18) 
y FreeDOS. La aplicación se ejecuta muy bien incluso en red (en una estacion 
sin disco duro que tengo) pero al salir del programa por segunda vez ocurre 
un "Segmentation Fault". Me podrias ayudar con este problema ? Mi ingles en 
realidad es demasiado malo y no creo que en la lista puedan entenderme.

Muchisimas gracias,

Haller Javier Bracho H.
hbracho@linux.org.ve


-
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

Re: Seg fault after quitting FoxPro 6 app

[Grigory Batalov]

On 19 Sep 2002 14:34:22 -0600
"Oscar A. Valdez" <oscar.valdez@plastipak.com.sv> wrote:

> A friend reports a segmentation fault after quitting a FoxPro 2.6
> application for the second time.
> 
> Dosemu: 1.0.2.1; Slackware 8.1 (kernel 2.4.18)
> 
> Hints and tips will be appreciated.

  You should try DOSMEM=ON in config.fp.

--
 Grigory Batalov.