Re: [jamboost] Re: build.bat change to help debug bjam crashes

From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-07-14 15:35:16

At 02:53 PM 7/14/2003, David Abrahams wrote:
>Beman Dawes <bdawes_at_[hidden]> writes:
>
>> I'm still getting occasional bjam crashes which disappear if the same
>> command is given a second time.
>>
>> It just happened again, so I ran a "build vc7 --debug" to get a debug
>> build. But there was no crash with this debug executable.
>>
>> Unfortunately, the debug build executable is so slow that it isn't
>feasible
>> to use it for all runs until the bug is captured.
>>
>> Would it be possible to modify build.bat to create a custom bjam.exe 
build
>
>> that does include debugging symbols, but otherwise is a release build?

My guess is that would be fine.

>Not quite easy, but I don't think you need optimization. Try checking
>out tools/build/jam_src again and building with --debug --noassert.

Didn't seem to have the desired effect. I assume a -DNDEBUG was expected. 
Below is the command line (-d2).

--Beman

cl /Febin.ntx86.debug\jam.exe -DOPT_HEADER_CACHE_EXT 
-DOPT_GRAPH_DEBUG_E
XT -DOPT_SEMAPHORE -DOPT_FIX_TARGET_VARIABLES_EXT 
-DOPT_IMPROVED_PATIENCE_EXT -D
NT -DYYSTACKSIZE=5000 /nologo /MLd /DEBUG /Z7 /Od 
/Ob0 "kernel32.lib" command
.c compile.c expand.c glob.c hash.c hcache.c headers.c hdrmacro.c jam.c 
jambase.
c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c regexp.c 
rules.c sc
an.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c 
built
ins.c pwd.c execnt.c filent.c pathunix.c