RSB set-builder Creates File Named "0"

[Joel Sherrill]

On Thu, Nov 29, 2018 at 1:19 PM Chris Johns <chrisj at rtems.org> wrote:

> On 30/11/18 6:08 am, Joel Sherrill wrote:
> > On Thu, Nov 29, 2018 at 1:03 PM Chris Johns <chrisj at rtems.org
> > <mailto:chrisj at rtems.org>> wrote:
> >     On 30 Nov 2018, at 4:27 am, Joel Sherrill <joel at rtems.org
> >     <mailto:joel at rtems.org>> wrote:
> >
> >>     Hi
> >>
> >>     I have been seeing this for a couple of weeks. I decided to watch a
> build
> >>     of the sparc
> >>     tools and see when it happened. I set a script to test for the
> existence
> >>     of 0 and kill the set-builder. In the rtems/ subdirectory of the
> RSB, the
> >>     script killed the set-builder when the gdb build started. So I think
> >>     something in the gdb bset file is creating this file.
> >
> >     It will be something related to the gdb python support I added:
> >
> >
> https://git.rtems.org/rtems-source-builder/tree/source-builder/config/gdb-common-1.cfg#n70
> >
> >     Does it happen with the —dry-run option?
> >
> > Yes.
> >
>
> Great that makes finding it easier.
>
> If you now add --trace does anything appear in the log that might be the
> cause?
>

Lots of 0's and I didn't see anything.

I put the l-sparc.txt.bz2 in /tmp on rtems.org.

--joel

>
> Chris
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20181129/a02b9ea5/attachment-0002.html>