ericr@hpvcfs1.HP.COM (Eric Ross) (02/28/89)
I just received my update to Zortech C++ (1.07e) and am trying to use it with Codeview version 2.2 (It came with my Masm 5.1). To keep things simple, I compiled the wc program that comes with the Zortech package using the -g option "ztc -g wc.c" and try to use Codeview. Codeview sees the line information and single steps through the program just fine, but I am unable to look at any local variables. Using the 'X?*' command, codeview lists all of the local variables in the current function, but it will not let me set watchpoints nor use the "?" command to see what their values are. Am I missing something? Any help would be appreciated. Other configuration info: Running MSDOS 3.3 on a Hewlett Packard Vectra RS/20 (80386). Thanks, Eric Ross hplabs!hpvcfs1!ericr ericr%hpvcper@hplabs.hp.com
usenet@cps3xx.UUCP (Usenet file owner) (02/28/89)
in article <1120002@hpvcfs1.HP.COM>, ericr@hpvcfs1.HP.COM (Eric Ross) says: > > I just received my update to Zortech C++ (1.07e) and am trying to > use it with Codeview version 2.2 (It came with my Masm 5.1). To keep > things simple, I compiled the wc program that comes with the Zortech > package using the -g option "ztc -g wc.c" and try to use Codeview. > Codeview sees the line information and single steps through the program > just fine, but I am unable to look at any local variables. Using > the 'X?*' command, codeview lists all of the local variables in the current > function, but it will not let me set watchpoints nor use the "?" command > to see what their values are. Am I missing something? > > Any help would be appreciated. > I've been using Zortech C++ v1.02 and Codeview, whatever version comes with MASM5.0. I believe I've been compiling with "ztc -g -co" and having it link with the MicroSoft Linker. What I've been doing to examine a local variable is when I get to a point at which I need to see a variable's value is change the source mode so that I see assembly code with the c lines interspersed as comments. From that you can easily find a variable's value. As 99.9% of my code doesn't use floats or doubles, this does not present any problem to me. Granted, it would be a lot easier to print local variables and use watchpoints. John H. Lawitzke UUCP: Work: ...rutgers!mailrus!frith!fciiho!jhl Michigan Farm Bureau ...decvax!purdue!mailrus!frith!fciiho!jhl Insurance Group ...uunet!frith!fciiho!jhl Home: ...uunet!frith!fciiho!ipecac!jhl