Dosemu 1.1.99.1 segfaults

DISCUSSION Stas Sergeev 3 participants 5 messages Oct 30, 2003 – Oct 31, 2003

lore

Share & tools

lore

Stas Sergeev

author

2003-10-30 19:53 UTC #0 lore raw

Hello.

Quoted 2 lines · Ged Haywood

Quoted 1 line
What kernel are you using? Some kind of 2.6?
2.6.0-test5

Dumb question actually, it was written in the beginning of the log...

Quoted 2 lines

Quoted 1 line
You have to upgrade your dosemu in that case.
Oh dear. Upgrade to what?

To CVS HEAD just as usual. It is known to be a good practice to update to CVS HEAD before reporting any bugs. That really helps and not only with dosemu.

Quoted 3 lines

Does it say that in the docs?
If so, where? I haven't found anything about kernel versions in the docs

But dosemu tells you every time you
start it:
---
Please test against a recent version before reporting bugs and problems.
---
Most people don't understand the importance
of that note. But probably now it must be
adjusted to reflect the fact that there is a
CVS in use.

Quoted 2 lines

If you will please tell me where or how to find the fix, I'll cease troubling you...

CVS repository of dosemu is the place where the fixes are now lingering.

Ged Haywood

2003-10-30 20:59 UTC #1 lore raw

Hi Stas,

Quoted 10 lines · Stas Sergeev

Quoted 3 lines
Does it say that in the docs?
If so, where? I haven't found anything about kernel versions in the docs
But dosemu tells you every time you
start it:
---
Please test against a recent version before reporting bugs and problems.
---
Most people don't understand the importance of that note. But probably now it must be adjusted to reflect the fact that there is a CVS in use.

Here's a patch for the docs...

- Please test against a recent version before reporting bugs and problems.
+ Please test against a very very very recent version before reporting bugs and problems.

I'll try CVS next.

73,
Ged.

Bart Oldeman

2003-10-30 21:12 UTC #2 lore raw

Quoted 13 lines · Ged Haywood

Quoted 10 lines · Stas Sergeev
Quoted 3 lines
Does it say that in the docs?
If so, where? I haven't found anything about kernel versions in the docs
But dosemu tells you every time you
start it:
---
Please test against a recent version before reporting bugs and problems.
---
Most people don't understand the importance of that note. But probably now it must be adjusted to reflect the fact that there is a CVS in use.

Quoted 8 lines

Here's a patch for the docs...
- Please test against a recent version before reporting bugs and problems.
+ Please test against a very very very recent version before reporting bugs and problems.
:)
I'll try CVS next.

it's more that the combination of a (still somewhat) bleeding edge kernel with dosemu has always been tricky at times, because dosemu by its very nature intimately interfaces with the kernel.

So I expect people who are brave enough to try 2.6 test kernels to be brave enough to search the mailing list archives for any clues about things that worked in 2.4.x and don't work in 2.6 :)

Bart

Ged Haywood

2003-10-30 21:30 UTC #3 lore raw

Hi Bart,

Quoted 1 line · Bart Oldeman

people who are brave enough to try 2.6 test kernels

Nothing brave about it: if I plug in a USB device with kernel 2.4.xx on my Athlon 1300 the kernel crashes, so I have to use 2.6 to get the photographs out of my camera... :(

Ged.

Ged Haywood

2003-10-31 16:02 UTC #4 lore raw

In reply to Ged Haywood

Hi Bart, Stas,

Quoted 1 line · Ged Haywood

I'll try CVS next.

Congratulations! Works fine with CVS.
I've been trying to compile this app under DOSEMU literally for years. Finally it's done. Thanks guys. Great stuff, now I can throw a DOS box away (well, turn it into a firewall or something:).

Here's the app compiled and zipped this morning under DOSEMU:
======================================================================
C:\SOS>pu -v sosppx4

= 80486 CPU detected.
= XMS version 3.00 detected.
= DPMI verrsion 0.90 detected.

Searching ZIP: SOSPPX4.ZIP

 Length  Method   Size  Ratio   Date    Time    CRC-32  Attr  Name
 ------  ------   ----- -----   ----    ----   -------- ----  ----
 583545  DeflatN 273217  54%  10-31-03  14:00  a1598864 --w-  SOSPPX4.EXE
 ------          ------  ---                                  -------

583545 273217 54% 1
======================================================================
and here's one I prepared earlier:

hurricane:$ >>> unzip -lv /mnt/hdb2/sos-source/sos-4.4260/sosppx4.zip

Archive:  sosppx4.zip
 Length   Method    Size  Ratio   Date   Time   CRC-32    Name
--------  ------  ------- -----   ----   ----   ------    ----
  583545  Defl:N   273217  53%  12-03-02 21:34  a1598864  sosppx4.exe
--------  ------  ------- -----   ----   ----   ------    ----

583545 273217 53% 1 file
======================================================================

A couple of comments:

1. There's something different about the memory allocation under DOSEMU. For the first pass of the Zortech C++ compiler to run without a stack fault when running under DOSEMU, I had to add a command line parameter to increase the default stack size (16384 bytes) substantially. Using 34148 bytes was enough, 34146 bytes wasn't. Never had to do that under the same version of DOS (6.22) running natively. This seems to me to be a surprisingly big difference and I wonder if it means something to you. If you want more information can investigate more easily when I'm back in England where the DOS box is. At present I'm doing all this remotely from France (which is why I'm doing it at all:) and I can't talk to it.

2. I gave you the full output of the pkunzip command above to show that it says "80486 CPU detected" when in fact it's running on a 686 with the dosemu.conf '$_cpu' variable set to "80586". I don't know whether pkunzip 2.04g is capable of recognizing a 586 so it might mean nothing.

If there's anything else you'd like me to try out on dosemu 1.3.0.0 while I have it running on Athlon/VIA/kernel 2.6.0 please let me know.

I've deleted bug number 832665.

73,
Ged.