www.digitalmars.com         C & C++   DMDScript  

c++.dos - How does one debug a DOS program?

reply Larry Brasfield <larry_brasfield snotmail.com> writes:
Hi.

I have been unable to discover a way to use the DMC IDE(s)
to debug a real-mode 16-bit DOS program.  I can create a
project, build it, run it successfully (in an NTVDM), but
I cannot run it or debug it from (any of) the IDE(s).

Was I confused when I got the notion that the product
supports DOS target development?  Is there some extra
component, not on the CD, needed for DOS debugging?

Thanks for any insight, including a clear statement that
DOS target debugging is just not possible with DMC.

-- 
-Larry Brasfield
(address munged, s/sn/h/ to reply)
Jul 25 2002
parent reply "Walter" <walter digitalmars.com> writes:
Check out the DOS app tutorial at:

www.digitalmars.com/ugr/chapter10.html

"Larry Brasfield" <larry_brasfield snotmail.com> wrote in message
news:MPG.17a9e2be1b8d944d989685 news.digitalmars.com...
 Hi.

 I have been unable to discover a way to use the DMC IDE(s)
 to debug a real-mode 16-bit DOS program.  I can create a
 project, build it, run it successfully (in an NTVDM), but
 I cannot run it or debug it from (any of) the IDE(s).

 Was I confused when I got the notion that the product
 supports DOS target development?  Is there some extra
 component, not on the CD, needed for DOS debugging?

 Thanks for any insight, including a clear statement that
 DOS target debugging is just not possible with DMC.

 --
 -Larry Brasfield
 (address munged, s/sn/h/ to reply)

Jul 25 2002
next sibling parent reply Cesar Rabak <csrabak uol.com.br> writes:
Walter wrote:
 
 Check out the DOS app tutorial at:
 
 www.digitalmars.com/ugr/chapter10.html
 

Do you folks have any idea of why the Environment->Workspace->New or Environment->Workspace->Clone are always grayed in my installation? I checked (what for me appeared to be) obvious files for not being read only, but did not find anything! -- Cesar Rabak GNU/Linux User 52247. Get counted: http://counter.li.org/
Jul 25 2002
next sibling parent reply "Walter" <walter digitalmars.com> writes:
"Cesar Rabak" <csrabak uol.com.br> wrote in message
news:3D409839.38659A51 uol.com.br...
 Walter wrote:
 Check out the DOS app tutorial at:

 www.digitalmars.com/ugr/chapter10.html

Do you folks have any idea of why the Environment->Workspace->New or Environment->Workspace->Clone are always grayed in my installation? I checked (what for me appeared to be) obvious files for not being read only, but did not find anything!

I don't know.
Jul 25 2002
parent Cesar Rabak <csrabak uol.com.br> writes:
Walter wrote:
 

 I checked (what for me appeared to be) obvious files for not being read
 only, but did not find anything!

I don't know.

Well, we can found a club them (we already have at least two prospect associates ;-) [] -- Cesar Rabak GNU/Linux User 52247. Get counted: http://counter.li.org/
Jul 27 2002
prev sibling parent reply Frank Albe <falbe mindspring.com> writes:
On Thu, 25 Jul 2002 21:30:49 -0300, Cesar Rabak <csrabak uol.com.br>
wrote:

Walter wrote:
 
 Check out the DOS app tutorial at:
 
 www.digitalmars.com/ugr/chapter10.html
 

Do you folks have any idea of why the Environment->Workspace->New or Environment->Workspace->Clone are always grayed in my installation? I checked (what for me appeared to be) obvious files for not being read only, but did not find anything!

I asked about this a few weeks ago. Got no answer. I dug around, it's even in the documentation somewhere. The limit is 5 workspaces. The IDE as delivered on the CD already has 5. Delete one. Then you can create or clone one. =:) ../frank
Jul 27 2002
next sibling parent "Walter" <walter digitalmars.com> writes:
Thanks, Frank! This is one for the FAQ. -Walter

"Frank Albe" <falbe mindspring.com> wrote in message
news:1j66ku06440kkedrg7h06r3l1bm8lgte4d 4ax.com...
 On Thu, 25 Jul 2002 21:30:49 -0300, Cesar Rabak <csrabak uol.com.br>
 wrote:

Walter wrote:
 Check out the DOS app tutorial at:

 www.digitalmars.com/ugr/chapter10.html

Do you folks have any idea of why the Environment->Workspace->New or Environment->Workspace->Clone are always grayed in my installation? I checked (what for me appeared to be) obvious files for not being read only, but did not find anything!

I asked about this a few weeks ago. Got no answer. I dug around, it's even in the documentation somewhere. The limit is 5 workspaces. The IDE as delivered on the CD already has 5. Delete one. Then you can create or clone one. =:) ../frank

Jul 27 2002
prev sibling parent Cesar Rabak <csrabak uol.com.br> writes:
Frank Albe wrote:
 
 On Thu, 25 Jul 2002 21:30:49 -0300, Cesar Rabak <csrabak uol.com.br>
 wrote:

Taking profit of this pointer:

Do you folks have any idea of why the Environment->Workspace->New or
Environment->Workspace->Clone are always grayed in my installation?

I checked (what for me appeared to be) obvious files for not being read
only, but did not find anything!

I asked about this a few weeks ago. Got no answer. I dug around, it's even in the documentation somewhere. The limit is 5 workspaces. The IDE as delivered on the CD already has 5. Delete one. Then you can create or clone one. =:)

-- Cesar Rabak GNU/Linux User 52247. Get counted: http://counter.li.org/
Jul 27 2002
prev sibling parent reply Larry Brasfield <larry_brasfield snotmail.com> writes:
In article <ahpja2$7j2$1 digitaldaemon.com>, 
Walter (walter digitalmars.com) says...
 Check out the DOS app tutorial at:
 
 www.digitalmars.com/ugr/chapter10.html

That's a great tutorial. Unfortunately, it leads to the same dead-end I stumbled into on my own. The tutorial mentions starting the IDE from the Program Manager 16-bit group, which has little relevance to my Windows 2000 machine. However, figuring that I can start .exe's by myself, I ran each of the following: SCWMN32.exe , SCWMN32S.exe , and SCWMN16.exe with the following results at the tutorial step instructing me to Start/Restart Debugging. At that point, the output window reports This debugger can only debug * applications. where '*' is either "Win32", "Win32s" or "16-bit Windows", depending on which IDE I run. I've tried running all the other .exe's in the DMC bin directory, but none of them start an IDE except the ones I mention above. At this juncture, I suspect there is an IDE installed by some older (Symantec) product that can run DOS applications, but which is not on the CD I got a few weeks ago. Could somebody tell me the name of the .exe that effects an IDE capable of debugging DOS targets? If it is one of the above, there must be some environment setting or other context it needs. If it is not one of the above, perhaps I could get a copy. I did find that the Win32 IDE would actually build and run the DOS program from the tutorial, it just won't debug it. Maybe there is a DLL debug-helper plug-in for DOS debugging? I'm glad to learn DOS debugging is (supposed to be) supported, but I'm still frustrated. Thanks for the help so far. -Larry
 "Larry Brasfield" <larry_brasfield snotmail.com> wrote in message
 news:MPG.17a9e2be1b8d944d989685 news.digitalmars.com...
 Hi.

 I have been unable to discover a way to use the DMC IDE(s)
 to debug a real-mode 16-bit DOS program.  I can create a
 project, build it, run it successfully (in an NTVDM), but
 I cannot run it or debug it from (any of) the IDE(s).

 Was I confused when I got the notion that the product
 supports DOS target development?  Is there some extra
 component, not on the CD, needed for DOS debugging?

 Thanks for any insight, including a clear statement that
 DOS target debugging is just not possible with DMC.


-- -Larry Brasfield (address munged, s/sn/h/ to reply)
Jul 26 2002
next sibling parent "John Lance" <JDLance prodigy.net> writes:
I seem to remember that in the upgrade from Symantec C++ Ver 7.5 to 7.6,
that you had to install over 7.5 to retain DOS debugging capability.

If you just installed 7.6 fresh, the DOS debugging was gone.

I don't know how relevent this is.  Walter should know or be able to find
out the full details and how it would apply here, if it does.
Jul 26 2002
prev sibling parent "Walter" <walter digitalmars.com> writes:
The trouble is that in order for the 16 bit debugger to work, it needs to
actually be running under win32s, which means a computer running 16 bit
Windows, not Win2000. Sorry.

On the bright side, though, any codeview or symdeb type debugger will work.
There is one called "D86" that claims to be able to source debug by reading
the linker .MAP file. I have not tried it myself.

I would love to be able to ship the 16 bit DOS Zortech debugger, but the
author has vanished and I have been quite unable to locate him to negotiate
a license. (If anyone knows where Phil Murray is, please let him know this!)

"Larry Brasfield" <larry_brasfield snotmail.com> wrote in message
news:MPG.17ab45b97fb27347989686 news.digitalmars.com...
 In article <ahpja2$7j2$1 digitaldaemon.com>,
 Walter (walter digitalmars.com) says...
 Check out the DOS app tutorial at:

 www.digitalmars.com/ugr/chapter10.html

That's a great tutorial. Unfortunately, it leads to the same dead-end I stumbled into on my own. The tutorial mentions starting the IDE from the Program Manager 16-bit group, which has little relevance to my Windows 2000 machine. However, figuring that I can start .exe's by myself, I ran each of the following: SCWMN32.exe , SCWMN32S.exe , and SCWMN16.exe with the following results at the tutorial step instructing me to Start/Restart Debugging. At that point, the output window reports This debugger can only debug * applications. where '*' is either "Win32", "Win32s" or "16-bit Windows", depending on which IDE I run. I've tried running all the other .exe's in the DMC bin directory, but none of them start an IDE except the ones I mention above. At this juncture, I suspect there is an IDE installed by some older (Symantec) product that can run DOS applications, but which is not on the CD I got a few weeks ago. Could somebody tell me the name of the .exe that effects an IDE capable of debugging DOS targets? If it is one of the above, there must be some environment setting or other context it needs. If it is not one of the above, perhaps I could get a copy. I did find that the Win32 IDE would actually build and run the DOS program from the tutorial, it just won't debug it. Maybe there is a DLL debug-helper plug-in for DOS debugging? I'm glad to learn DOS debugging is (supposed to be) supported, but I'm still frustrated. Thanks for the help so far. -Larry
 "Larry Brasfield" <larry_brasfield snotmail.com> wrote in message
 news:MPG.17a9e2be1b8d944d989685 news.digitalmars.com...
 Hi.

 I have been unable to discover a way to use the DMC IDE(s)
 to debug a real-mode 16-bit DOS program.  I can create a
 project, build it, run it successfully (in an NTVDM), but
 I cannot run it or debug it from (any of) the IDE(s).

 Was I confused when I got the notion that the product
 supports DOS target development?  Is there some extra
 component, not on the CD, needed for DOS debugging?

 Thanks for any insight, including a clear statement that
 DOS target debugging is just not possible with DMC.


-- -Larry Brasfield (address munged, s/sn/h/ to reply)

Jul 26 2002