kicad-developers team mailing list archive

[Seth Hillbrand <seth@xxxxxxxxxxxxx>]

Ah, thanks!

Looks like that was fixed in master but didn't get cherry-picked.  The fix
is in the v6 branch now.

Seth

On Fri, May 6, 2022 at 11:08 AM Ian McInerney <ian.s.mcinerney@xxxxxxxx>
wrote:

> The second bug appears to be an assertion due to an invalid vector access.
>
> The stack trace is below.
>
> Truncated backtrace:
> Thread no. 1 (10 frames)
>  #2 std::__replacement_assert at
> /usr/include/c++/11/x86_64-redhat-linux/bits/c++config.h:2660
>  #3 std::vector<VECTOR2<int>, std::allocator<VECTOR2<int> > >::operator[]
> at /usr/include/c++/11/bits/stl_vector.h:1043
>  #5 ZONE::HatchBorder at
> /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/zone.cpp:1031
>  #6 ZONE::SetBorderDisplayStyle at
> /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/zone.cpp:882
>  #7 PCB_PARSER::parseZONE at
> /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_parser.cpp:5437
>  #8 PCB_PARSER::parseFOOTPRINT_unchecked at
> /usr/include/c++/11/bits/unique_ptr.h:173
>  #9 PCB_PARSER::parseFOOTPRINT at
> /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_parser.cpp:3211
>  #10 PCB_PARSER::Parse at /usr/include/c++/11/bits/unique_ptr.h:185
>  #11 FP_CACHE::Load at
> /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_plugin.cpp:274
>  #12 PCB_PLUGIN::FootprintEnumerate at
> /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_plugin.cpp:2390
>
>
> This is trying to read the
> `/usr/share/kicad/footprints//RF_Module.pretty/MOD-nRF8001.kicad_mod` file
> provided in the standard footprint library (and apparently there is an
> extra slash entering the path somewhere, but that is extraneous to this).
> What seems to be happening is that during the parsing, it is finding a
> hatched zone, but the hatch border has an empty pointbuffer, which then
> causes the stdlib assert to fire when it is accessed at any index.
>
> -Ian
>
> On Fri, May 6, 2022 at 7:00 PM Seth Hillbrand <seth@xxxxxxxxxxxxx> wrote:
>
>> Hi Steven-
>>
>> The second bug is locked down.  We can't see it without proper access
>> credentials.
>>
>> Seth
>>
>> On Fri, May 6, 2022 at 6:45 AM Steven A. Falco <stevenfalco@xxxxxxxxx>
>> wrote:
>>
>>> There are two SIGABRT bugs reported on Fedora:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=2079984
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=2082394
>>>
>>> The first bug was closed because it was not able to be reproduced.  The
>>> second one has apparently happened to the reporter several times, but again
>>> I don't know if it is reproducible on demand.
>>>
>>> Do either of these ring a bell with anyone?
>>>
>>>         Steve
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>> --
>> [image: KiCad Services Corporation Logo]
>> Seth Hillbrand
>> *Lead Developer*
>> +1-530-302-5483‬
>> Long Beach, CA
>> www.kipro-pcb.com    info@xxxxxxxxxxxxx
>> _______________________________________________
>> 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
>>
>

-- 
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483‬
Long Beach, CA
www.kipro-pcb.com    info@xxxxxxxxxxxxx