Re: [jamboost] A different bjam crash

From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-07-26 09:57:50

[2003-07-26] Beman Dawes wrote:

>At 10:10 AM 7/26/2003, Michael Stevens wrote:
>
> >I've been following your crashes with interest! What is for certain is
> >that a memory corruption is going to really hard to find. The idea that
> >it could be a compiler bug (or compatiblity problem) got me thinking
> >about ways to narrow down the possibilites. I have a suggestion which
> >comes a bit from left field! Would it be possible for you to keep
> >everything the same but run with "bjam" compiled with gcc or another
> >compiler.
>
>Yes, I've thought about that too. I've been hoping that seeing the stack 
>trace would ring a bell with someone.

I've been looking at the traces and looked at code. Nothing seems to spring
forward as a cause :-( ... so far.

>I've hesitated to try another compiler because I'm not familiar with their 
>debuggers. But if no other ideas surface within the next day or two, I'll 
>give Metrowerks a try.

Don't hesitate, if you CW you can still use the VC debugger. Of course if
you had a memory debugging utility, like valgrind on Linux, that would
probably be of tremendous help.

-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq