Not really highlighted much, but the new StackFrame class gives some very
useful debugging techniques. I just used a couple of these to figure out a
problem.
If you are interactive trace mode and want to find out how you got to a
specific place, issue the command
say
If you want to see what are getting used for the compile and links, you can
specify nmake VERBOSE=1, and it will display all of the commands that
nmake is issuing. This allows you to see the exact commands getting issued
for the build steps.
Rick
On Sun, Jun 15, 2014 at 4:37 PM, Mark Miesfeld
Thanks Rick.
--
Mark Miesfeld
On Sun, Jun 15, 2014 at 2:06 PM, Rick McGuire object.r...@gmail.com wrote:
If you want to see what are getting used for the compile and links, you
can specify nmake VERBOSE=1, and it will display all of the commands that
nmake is issuing. This allows you to
Shoot, I stand corrected. It appears nmake writes all of the options to a
temp file and uses
C:\PROGRA~2\MICROS~3.0\VC\bin\amd64\cl.exe
@C:\Users\RICKMC~1\AppData\L
ocal\Temp\nm4144.tmp
to invoke the compler and linker. The options are not showing up in
verbose mode. This will
Okay, yeah I discovered the temp files. Unfortunately during the build the
files get deleted to fast to look at them.
--
Mark Miesfeld
On Sun, Jun 15, 2014 at 2:21 PM, Rick McGuire object.r...@gmail.com wrote:
Shoot, I stand corrected. It appears nmake writes all of the options to a
temp
I don't have time to do the link, but adding an echo did work. Here is the
value of the CXX_FLAGS for compiling the files in rexx.dll. I don't have
time to compare these to the old build right now:
CXX_FLAGS=/DWIN32
/D_WINDOWS
/W3
/GR
/EHsc
/D_DEBUG
/MDd
/Zi
/Ob0
/Od
/RTC1
There is also a file in the make files directory, for example under
rexx.dir, flags.make.
It shows:
CXX_FLAGS = /DWIN32 /D_WINDOWS /W3 /GR /EHsc /D_DEBUG */MDd* /Zi /Ob0 /Od
/RTC1 -IC:\work.ooRexx\wc\main\api\platform\windows
-IC:\work.ooRexx\wc\main\api -
...
So, the DLLs are getting linked
Ok, should be pretty easy to fix this. A few questions:
1) Does this apply to both .exes and .dlls?
2) Does it apply to all of the applicable types?
3) Is the option the same for both release and debug versions?
Rick
On Sun, Jun 15, 2014 at 6:36 PM, Mark Miesfeld miesf...@gmail.com wrote:
I see you figured this out already. Was it really necessary to set the
_DEBUG and _RELEASE flags? I suspect the top level version would be
sufficient.
Rick
On Sun, Jun 15, 2014 at 9:04 PM, Rick McGuire object.r...@gmail.com wrote:
Ok, should be pretty easy to fix this. A few questions:
1)
Well, both the release and debug flags need it. I don't know about any top
level version.
It did fix the crashes I was seeing.
In the debug version at list, CMake has a -RTC1 flag that enables run time
error checking. We weren't using that flag. This seems like a good flag
to use, maybe. It
10 matches
Mail list logo
