kicad-developers team mailing list archive

[Diego Herranz <diegoherranz@xxxxxxxxxxxxxxxx>]

Hi, all.

I'm using nightlies and facing a weird bug with buses. I was wondering
whether it can be related to these bus upgrades.

I've got a bus:
ROW0, ROW1, ROW2, ROW3, ROW4, ROW5, ROW6, ROW7, which on the PCB layout
becomes
ROW0, ROW0, ROW0, ROW0, ROW0, ROW0, ROW0, ROW7 ???
It seems to be semi-random and I've seen other combinations too.

I've managed to reduce the SCH to a minimal example (link below). Further
changes to this seem to fix it somehow, so I couldn't reduce it anymore.
Note that one of the symbols is not on the official library so I've
included a local library.
I've tried replacing that symbol for a standard header, but that seems to
fix the problem, although I can't see anything wrong with the symbol itself.

Can anyone confirm that it is a bug and not something I'm doing wrong?
Is it related to this upgrade?
Please let me know how to proceed. I can report the bug on launchpad.

Many thanks!

 bus_bug.zip
<https://drive.google.com/file/d/1K7tWvM5M8F-Y-2bBwAPGBKG7O452hcrL/view?usp=drive_web>


Application: KiCad
> Version: 6.0.0-unknown-6b031d9~100~ubuntu16.04.1, release build
> Libraries:
>     wxWidgets 3.0.2
>     libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
> Platform: Linux 4.4.0-157-generic x86_64, 64 bit, Little endian, wxGTK
> Build Info:
>     wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
>     Boost: 1.58.0
>     OpenCASCADE Community Edition: 6.8.0
>     Curl: 7.47.0
>     Compiler: GCC 5.4.0 with C++ ABI 1009
> Build settings:
>     KICAD_SCRIPTING=ON
>     KICAD_SCRIPTING_MODULES=ON
>     KICAD_SCRIPTING_PYTHON3=OFF
>     KICAD_SCRIPTING_WXPYTHON=ON
>     KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
>     KICAD_SCRIPTING_ACTION_MENU=ON
>     BUILD_GITHUB_PLUGIN=ON
>     KICAD_USE_OCE=ON
>     KICAD_USE_OCC=OFF
>     KICAD_SPICE=ON


On Wed, 3 Apr 2019 at 19:01, Jon Evans <jon@xxxxxxxxxxxxx> wrote:

> I can move to stdlib regex; I'll look in to that later this week.
>
> On Wed, Apr 3, 2019 at 1:44 PM Wayne Stambaugh <stambaughw@xxxxxxxxx>
> wrote:
>
>> Tom,
>>
>> On 4/3/2019 1:34 PM, Tomasz Wlostowski wrote:
>> > On 02/04/2019 17:27, Wayne Stambaugh wrote:
>> >> We should always be using wxLogTrace.  Using printf and cout are
>> >> meaningless on windows and wxLogDebug means that your debugging output
>> >> is always spewed on debug builds even when it's not needed.  I haven't
>> >> made the draconian move of making this policy but maybe I should since
>> >> we seem to be leaving lots of debugging code in all manner of formats
>> in
>> >> our source code.
>> >>
>> > @Wayne Can I somehow use wxLogTrace() on release builds?
>>
>> Unfortunately no.  All of the wxLog macros compile away in release builds.
>>
>> >
>> > @Jon I just tried to build today's master and it complained about
>> > missing boost::regex library. There is regexp support in libstdc++ in
>> > C++11, why go for boost?
>>
>> I got bit by this too on Debian.  I think boost packaging on Debian is
>> in a state of flux the moment.  I see the boost-dev package is being
>> held back even when I do a dist-upgrade.  This is (was) the package that
>> used to pull in all of boost and it's libraries.  Maybe there is a new
>> meta package that does that.  I just installed boost-regex-dev and all
>> was well.
>>
>> >
>> > Tom
>> >
>>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>