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

Debugging DOS code #4

Open
ronny332 opened this issue Dec 30, 2017 · 1 comment
Open

Debugging DOS code #4

ronny332 opened this issue Dec 30, 2017 · 1 comment
Assignees
Labels

Comments

@ronny332
Copy link

Hi,
it looks like a similar issue for DOS debugging (please refer to #2) still exists in the current version. I just tried to move an existing small assembly program over to visual masm and the output indicates that again the quotes are at the wrong place:

"c:\masm32\bin\ml.exe /Zi /Zd /Zf" /Fo"C:\Users\noname\Documents\Visual MASM\Test-01\Debug\Assembly1.obj" /c /AT /nologo "C:\Users\noname\Documents\Visual MASM\Test-01\Assembly1.asm

Without any quotes around the ml.exe and an extra space ight after the /Fo switch it is running smoothly:

c:\masm32\bin\ml.exe /Zi /Zd /Zf /Fo "C:\Users\noname\Documents\Visual MASM\Test-01\Debug\Assembly1.obj" /c /AT /nologo "C:\Users\noname\Documents\Visual MASM\Test-01\Assembly1.asm

The way these query strings get built is not configurable from the users side, right?

@ThomasJaeger
Copy link
Owner

This is fixed now. Thank you for reporting this. So, the command line switches are built by Visual MASM and are not configurable. The only portions that you can do from a users point of view is to create all your command line switches in the projects options. There you have full control.

Let me know if this works for you now.

@ThomasJaeger ThomasJaeger self-assigned this Dec 30, 2017
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

3 participants
@ThomasJaeger @ronny332 and others