does it happen if you type rescan at the dosbox prompt ?
I had a DOS program rescan.exe in my path already that was called when I
typed rescan at the dosbox prompt.
I could remove it from the path and try again I suppose.
DOSBox has a built in command called rescan which clears caches rela
Peter Veenstra wrote, on 2009-01-12 00:03:
Some ideas/tests to check for the leak.
Does the memory return once the batch file ends ?
No.
does it happen if you type rescan at the dosbox prompt ?
I had a DOS program rescan.exe in my path already that was called when I
typed rescan at the do
Some ideas/tests to check for the leak.
Does the memory return once the batch file ends ?
does it happen if you type rescan at the dosbox prompt ?
could you give some sort of outline how the bat file works.
does it happen as well if you type core=normal before starting everything
?
On Sat, 10
Peter Veenstra wrote, on 10/01/09 20:08:
valgrind maybe ?
Is the batchfile calling itself ?
Yes.
As dosbox destroys a batch file
handler at the end of the bat file, so it is possible that there are lot
of bat files created.
Would simpler arrangements where batch files don't call themselv
valgrind maybe ?
Is the batchfile calling itself ? As dosbox destroys a batch file handler
at the end of the bat file, so it is possible that there are lot of bat
files created.
On Wed, 7 Jan 2009, Arthur Marsh wrote:
Package: dosbox
Version: 0.72-1.1
Severity: normal
Hi, when attemptin
Package: dosbox
Version: 0.72-1.1
Severity: normal
Hi, when attempting to run a complex batchfile used for running a
Fidonet mailer and bbs I noticed the memory usage increasing above 300
Megabytes.
Are there any prefered ways of debugging this problem?
-- System Information:
Debian Release:
6 matches
Mail list logo
