[Scons-users] How to debug infinite loop?

Bill Deegan bill at baddogconsulting.com
Fri Jan 24 10:11:15 EST 2020


So this is not an infinite loop. But rather some commands you're running
filling up the all the build slots because they are hanging?


On Fri, Jan 24, 2020 at 3:27 AM Daan De Meyer <daan.j.demeyer at gmail.com>
wrote:

> I debugged the issue by using `pgrep -P <scons-pid>` to list the child
> pid's of scons which gave me the pid of the process that was hanging. `ps
> -aux | grep <child-pid>` then gave me the command line of the process that
> was hanging. Of course this only works if a separate process is spawned for
> the hanging command.
>
> Regards,
>
> Daan De Meyer
>
> On Thu, 23 Jan 2020 at 17:49, Bill Deegan <bill at baddogconsulting.com>
> wrote:
>
>> Sounds like one of your processes was hanging?
>>
>> On Thu, Jan 23, 2020 at 10:07 AM Mats Wichmann <mats at wichmann.us> wrote:
>>
>>> On 1/23/20 4:17 AM, Daan De Meyer wrote:
>>> > 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.
>>>
>>> And were you able to resolve the issue?
>>>
>>> If so, a quick analysis might be something we should drop onto the wiki
>>> for future generations....
>>>
>>>
>>> _______________________________________________
>>> 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/20200124/ca9c6e47/attachment.html>


More information about the Scons-users mailing list