Re: [Boost-build] Debugging Boost Build problems

Subject: Re: [Boost-build] Debugging Boost Build problems
From: Edward Diener (eldiener_at_[hidden])
Date: 2017-02-18 05:18:55

On 2/17/2017 5:17 PM, Steven Watanabe via Boost-build wrote:
> AMDG
>
> On 02/17/2017 02:07 PM, Rene Rivera via Boost-build wrote:
>> On Fri, Feb 17, 2017 at 3:03 PM, Edward Diener via Boost-build <
>> boost-build_at_[hidden]> wrote:
>>
>>> In an effort to debug Boost Build problems I create a branch of my own
>>> from Boost Build and then add ECHO commands in jam source files whenever I
>>> want to look at anything that is happening when executing b2. Is there a
>>> better way ?
>>>
>>
>> Steven wrote debugger support <https://github.com/boostorg/build/tree/debug>.
>> Not sure what the state of it is. But you could give that a try.
>>
>
> Basic usage should work without problems:
> - Program execution: step/next/finish/continue
> - Breakpoints: By line # or function name
> - printing expressions
> - help gives a list of commands (without explanation).

Do you mean 'b2 --help' ? Does not seem to tell me anything about your 
debugger. How do I start your b2 debugger ?

> Not supported:
> - examining variables in outer stack frames (Dynamic
>   scope makes this really painful to implement.)
> - editor/IDE support (I got it to work with Emacs
>   GDB mode in the past, but this is currently broken).
>
> The test case should exercise everything that's currently implemented:
> https://github.com/boostorg/build/blob/debug/test/debugger.py
>
> Also, it's been a while since I updated it, so it may
> be out of sync with the current develop branch.
>
> In Christ,
> Steven Watanabe