Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default command.com crashed when called recursively certain times #5411

Open
2 tasks done
qfcy opened this issue Jan 16, 2025 · 0 comments
Open
2 tasks done

Default command.com crashed when called recursively certain times #5411

qfcy opened this issue Jan 16, 2025 · 0 comments
Labels

Comments

@qfcy
Copy link

qfcy commented Jan 16, 2025

Describe the bug

When executing:

@echo off
rem the `mem` command is removable since it's only for debugging
mem
rem recursively calls command.com
%comspec% /c %0

the DOSBox-X crashed even before exhausting the whole memory:
Image

When I changed the line to %comspec% /c %comspec% /c %0, the bug appeared as usual, but the amount of memory is slightly different:
Image

Steps to reproduce the behaviour

1.Download any latest DOSBox-X versions (as this bug appears on nearly all specific versions, even on older DOSBox 0.74 or DOSBox SVN) .
Create a batch file and save it as recurse.bat in the same directory as dosbox-x.exe:

@echo off
rem the `mem` command is removable since it's only for debugging
mem
%comspec% /c %0

It's advisable not to directly open it since it can directly be run on Windows.
2.Run it via dragging the recurse.bat to dosbox-x.exe in Windows Explorer, or open dosbox-x.exe and input:

mount c .
c:
recurse

Then you will see Werfault.exe unexpectedly appear in Windows Task Manager.

Expected behavior

The batch file runs normally until all the conventional memory is exhausted.
When the memory is exhausted, DOSBox should display a message like "Program too big to fit in memory" similar to the behavior of MS-DOS.

What operating system(s) this bug have occurred on?

Windows 10 22H2 (note: the screenshot shows my win7 theme, but it is actually on win10)

What version(s) of DOSBox-X have this bug?

2025.01.01 SDL2 MinGW, commit 895fca3

Used configuration

I used the default configuration.

Output log

No any infomation relevant to this bug are output, even in debugger window (See the additional information section)

Additional information

The debugger window not outputting any message:
Image

The output when executing the same file in DOSBox-SVN debugger that might offer some help:
Image

Have you checked that no similar bug report(s) exist?

  • I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

  • I agree to follow the code of conduct and the contributing guidelines.
@qfcy qfcy added the bug label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant