[Scons-users] How to debug infinite loop?

[Daan De Meyer]

I tried that but it doesn't tell me which tasks are still running when
scons blocks. However, I managed to find the problematic commands by simply
checking the child processes spawned by scons when it blocked.

Regards,

Daan De Meyer

On Thu, 23 Jan 2020 at 12:07, Mats Wichmann <mats at wichmann.us> wrote:

> On January 23, 2020 12:53:54 AM MST, Daan De Meyer <
> daan.j.demeyer at gmail.com> wrote:
>>
>> Hi,
>>
>> I'm trying to get parallel builds working with a legacy SCons build.
>> We're using version 3.0.1 and when building with more than 1 job, after a
>> while the taskmaster always gets stuck at the same spot with the message:
>> "Taskmaster: Looking for a node to evaluate, Taskmaster: No candidate
>> anymore.".
>>
>> I'm pretty sure the fault is in our usage of SCons and not SCons itself.
>> I think some of our tasks are getting stuck in an infinite loop when SCons
>> uses more than one job. However, as there's a large amount of SCons scripts
>> that could be causing the issue, It would be great if I could get SCons to
>> list the current tasks that are in progress when it gets stuck in an
>> infinite loop. That would at least give me an indication as to which part
>> of the build is causing the issue.
>>
>> Does SCons provide anything that would help me further debug this issue?
>>
>> Regards,
>>
>> Daan De Meyer
>>
>>
>>
> try the --taskmastertrace option
> --
> Sent from a mobile device with K-9 Mail. Please excuse my brevity.
> _______________________________________________
> Scons-users mailing list
> Scons-users at scons.org
> https://pairlist4.pair.net/mailman/listinfo/scons-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist4.pair.net/pipermail/scons-users/attachments/20200123/54d71465/attachment.html>