X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1598818011; bh=Jvc4U9iYy48xZAGwp2JG3ckjuyyWFdpWExzD+T/cQxs=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=e6I+f6nE8fvO0TLpGgKHwWdgKbNkQ/SQNuRVtuyXyTTygfLtus6p4jukicEBZAcCu 5+Nj9r3vya1+BFrr6CHYCXVaPlJLT5ADfGupC2FWMC7K1Q4YdbnNsHW6qI8/+G6+xR 2Ar6whkhg3OPcV21F9s/nLo+x39QGVqf4pEzeAkY= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Subject: Re: SIGSEGV when trying to compile helloworld To: djgpp AT delorie DOT com References: <835z90xgab DOT fsf AT gnu DOT org> <833644xdzz DOT fsf AT gnu DOT org> From: "sleepy_dog AT gmx DOT de [via djgpp AT delorie DOT com]" Message-ID: <49d6271c-84bb-cd02-4ab6-bdc5342af0ce@gmx.de> Date: Sun, 30 Aug 2020 22:06:49 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------75BD6D0E74AE5CF3185B4F98" X-Provags-ID: V03:K1:OG7VdAZ4eiwsNQjyVsHFWQ9JqORlhbS2lScGr1GSAkRLvkUKhEg op1Zdrf84DHaVacOr1sswUML2jr2uTUiNaN8ky2JbEj7oybPG07cYdO0vuKhgM9Q9h12RuC bUi6N4nZWJdbD44bGZXwuO01E3WH67tvcoFYBx7ON7xCJcLfwXkGgULdT7YhQVxISK8qaNJ 0A/JwpB9XoQwYgRPwexHQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:UpiWZX8Ra4I=:49HAf8M/WaF7lFRi3y0l+w ISNHbvPNLZhxHCHC9NI+L2BpJBo/3knitA8C42XvhuA7dPdBetothPrYfivtw0pwSlFiA+14I c6GT0V3GkT612P6s9VA9OTIgQC/JrYjYldlVZrOzwSkEmW5PZF7/wwCiP7idTr6RY5OB7YlEa d8FeVYeJXArSip/IhalyKj/PRxh95oj4pii81up19lBBfU2eWDi5nH7toV8Qp3k4YUAjcrQLE RvNLyrmK+XvF3PMhuX7yrivIeqvq3Nb9kpQ3H2NgmHgc8UPKXH6NNxpIfoJEhnda8dcxeJCYd dQBFLbT/aqnhoFgJoL75uejCOEvcnTXkEWe7yqWhYsAMZ4nLvjkK+WdXq1OT7vMnduvHTv0zV 61IDEOvwZay0fqLwj/aCtLas+58+eae52o+9kerqz2y+jMZm8W+OjogpdYRKJYRCwPwirUkOD dRhT8XiHZEUCNXBwUl+GErXCtdPdcgiYGCPi6hY10tZACt2cP4+RmByFhs1gNQWiew3pu/wlG Wr1JX2XGPgGXGEh8fpsZSr4WK46CydzaUaAdG3l4kN73OtmBm8rvOTt0RLM6V6VMafkYGSKtS ZUrIBUeJ4cuGzZTuzbsPKZFc51z56FvX5lWzXBtH2rcGOprjMA8kd8Bv7ZZ2O0KsySBpE3wog r4rBbAm27IJnIb5j9OJbFD4rTE9Y8cv1SMxrlreovX9xHVu0Fver36m/W2fWUKu8k9Iykjmtf hOSRdexDQ5blkrkXpjeAOlg6nJmi5i2YfcpTWF+s7QAdgdVWezal474ME5ITREcrwN5YrTpZq 9iZp6LLG5+1d4q6TPwxGxWzQ/HWaiqQp1jbFweZvfaCePJCNtJwW82zVJ9wAyZRxS011pJtaz D1yGAsevbTo1XyJfi5RPeP/pxFuLhieuXUzS4pXsmgZbKBQcyv8ef8NKmW6sfLNnxbqqnVrJ4 2V+R+zeEy6nnVWxU3jbjgwV2daiQOIdkxjF1EuxFfVkLdp+jzlYVE9dxmw0iT+RS94inAUtWJ 2LJsv4K+8TR7bLAGcJHnsXPtT/tYTRQD4SITG6F8GkFZHo3GWKj5of2MSZ2qtTvshP1uJKM3P +kzkP3wx71J3UwS05YOG2rLpkj36dGq/ueIbJOwzT0NCJPZM9HYurSTelKaHgnJyM2cmq9XLV 1P++vxXoSBh8H/12sGQ5mpoAxmfLRy6IKPpAzCtZ4OQOfZT6058UKE8nr1J2JnlvPOvIeymi7 pN/DjzB2Fs1knWqDnYRphtRYBLp8cCuRZ2ANBjQ== Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk This is a multi-part message in MIME format. --------------75BD6D0E74AE5CF3185B4F98 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable can't find anything about resync, though > > Ah! Resync. I didn't know that. I had heard of sync'ing problems with > DOSBox & file system and seen myself that files created from the host > OS after starting DOSBox aren't showing up. > Will try that. Lack of long file names in DOSBox is kind of a pain, > though. > >> DOSBox provides a (mostly) elegant solution to this -- just share >> your files directly. Unlike other VMs, DOSBox allows you to directly >> mount the host filesystem within the DOS VM -- so you can just edit >> the files directly using your editor of choice on Windows, then >> switch to DOSBox and build them. (You do need to watch out for long >> filenames, though.) In the odd occurrence of being out of sync, the >> DOSBox command "resync" will refresh its cached directory of the host F= S. >> >> Damian >> >> >> On Sun, Aug 30, 2020 at 12:09 PM sleepy_dog AT gmx DOT de >> [via djgpp AT delorie DOT com >> ] > > wrote: >> >> Hi, >> >> > I thought he was running DJGPP under DOSBox and not directly >> under Windows 7. >> >> No no, I planned to make the programs run under DOSbox, but >> compiling is from within windows. >> I guess for debugging I would have to use RHIDE within DOSbox, >> esp. because Graphics modes are involved. >> But I'd prefer not to use it as an actual editor. >> >> > How about trying some other kind of virtual machine, eg. QEMU >> or VMWare? >> >> I was now thinking of running a VirtualBox WinXp32 image on my >> system, >> with a shared folder for the sources, and a build script I >> trigger manually. >> That would be somewhat workable, I guess. >> >> I have no experience with QEMU or VMWare, and interoperability with >> stuff that runs on the host system. >> >> >> > Hi all, >> > >> > On Sun, 30 Aug 2020 at 17:10, Eli Zaretskii (eliz AT gnu DOT org >> ) [via >> > djgpp AT delorie DOT com ] >> > wrote: >> >>> From: "sleepy_dog AT gmx DOT de [via >> djgpp AT delorie DOT com ]" > > >> >>> Date: Sun, 30 Aug 2020 18:32:41 +0200 >> >>> >> >>> go32/v2 version 2.0 built Oct 18 2015 09:41:08 >> >>> Usage: go32 coff-image [args] >> >>> Rename this to go32.exe only if you need a go32 that can run >> v2 binaries as >> >>> well as v1 binaries (old makefiles). Put ahead of the old >> go32 in >> >>> your PATH >> >>> but do not delete your old go32 - leave it in the PATH >> after this one. >> >>> Set GO32_V2_DEBUG=3Dy in the environment to get verbose output. >> >>> >> >>> DPMI memory available: 704964 Kb >> >>> DPMI swap space available: 0 Kb >> >>> >> >>> Hm. DPMI swap space 0 =3D bad? >> >> No, that's OK. Many "modern" DPMI providers just lump all the >> memory >> >> together (700MB in your case), and don't bother separating >> them into >> >> RAM and swap. >> >> >> >> The memory amount sounds enough, so I'm puzzled what could be th= e >> >> problem. Maybe some Windows 7 specific problem? I think someon= e >> >> posted here long ago tricks to get the Windows DPMI provider mor= e >> >> friendly... Anyone? >> > I thought he was running DJGPP under DOSBox and not directly unde= r >> > Windows 7. DOSBox is designed to be able to run old games, so no= t >> > even long filenames are implemented. How about trying some >> other kind >> > of virtual machine, eg. QEMU or VMWare? >> > >> > I've said it before, but NT series Windows support for DOS >> programs is >> > pathetic (and on 64-bit versions it is nonexistent). Then again, >> > Linux never directly supported DOS programs at all. In both case= s, >> > virtual machines are the solution. >> > >> > Cheers, >> > Albert. >> > >> >> > --------------75BD6D0E74AE5CF3185B4F98 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
can't find anything about resync, though

Ah! Resync. I didn't know that. I had heard of sync'ing problems with DOSBox & file system and seen myself that files created from the host OS after starting DOSBox aren't showing up.
Will try that. Lack of long file names in DOSBox is kind of a pain, though.

DOSBox provides a (mostly) elegant solution to this -- just share your files directly. Unlike other VMs, DOSBox allows you to directly mount the host filesystem within the DOS VM -- so you can just edit the files directly using your editor of choice on Windows, then switch to DOSBox and build them. (You do need to watch out for long filenames, though.) In the odd occurrence of being out of sync, the DOSBox command "resync" will refresh its cached directory of the host FS.

Damian


On Sun, Aug 30, 2020 at 12:09 PM sleepy_dog AT gmx DOT de [via = djgpp AT delorie DOT com] <djgpp AT delorie DOT com> wrote:
Hi,

> I thought he was running DJGPP under DOSBox and not directly under Windows 7.

No no, I planned to make the programs run under DOSbox, but compiling is from within windows.
I guess for debugging I would have to use RHIDE within DOSbox, esp. because Graphics modes are involved.
But I'd prefer not to use it as an actual editor.

> How about trying some other kind of virtual machine, eg. QEMU or VMWare?

I was now thinking of running a VirtualBox WinXp32 image on my system,
with a shared folder for the sources, and a build script I trigger manually.
That would be somewhat workable, I guess.

I have no experience with QEMU or VMWare, and interoperability with
stuff that runs on the host system.


> Hi all,
>
> On Sun, 30 Aug 2020 at 17:10, Eli Zaretskii (eliz AT gnu DOT org) [via
> djgpp AT de= lorie.com] <djgpp AT de= lorie.com> wrote:
>>> From: "sleepy_d= og AT gmx DOT de [via djgpp AT de= lorie.com]" <djgpp AT de= lorie.com>
>>> Date: Sun, 30 Aug 2020 18:32:41 +0200
>>>
>>> go32/v2 version 2.0 built Oct 18 2015 09:41:08 >>> Usage: go32 coff-image [args]
>>> Rename this to go32.exe only if you need a go32 that can run v2 binaries as
>>>=C2=A0 =C2=A0 well as v1 binaries (old makefiles).= =C2=A0 Put ahead of the old go32 in
>>> your PATH
>>>=C2=A0 =C2=A0 but do not delete your old go32 - le= ave it in the PATH after this one.
>>> Set GO32_V2_DEBUG=3Dy in the environment to get verbose output.
>>>
>>> DPMI memory available: 704964 Kb
>>> DPMI swap space available: 0 Kb
>>>
>>> Hm. DPMI swap space 0 =3D bad?
>> No, that's OK.=C2=A0 Many "modern" DPMI providers jus= t lump all the memory
>> together (700MB in your case), and don't bother separating them into
>> RAM and swap.
>>
>> The memory amount sounds enough, so I'm puzzled what could be the
>> problem.=C2=A0 Maybe some Windows 7 specific problem?= =C2=A0 I think someone
>> posted here long ago tricks to get the Windows DPMI provider more
>> friendly...=C2=A0 Anyone?
> I thought he was running DJGPP under DOSBox and not directly under
> Windows 7.=C2=A0 DOSBox is designed to be able to run old games, so not
> even long filenames are implemented.=C2=A0 How about tryi= ng some other kind
> of virtual machine, eg. QEMU or VMWare?
>
> I've said it before, but NT series Windows support for DOS programs is
> pathetic (and on 64-bit versions it is nonexistent).=C2= =A0 Then again,
> Linux never directly supported DOS programs at all.=C2=A0= In both cases,
> virtual machines are the solution.
>
> Cheers,
> Albert.
>




--------------75BD6D0E74AE5CF3185B4F98--