Le 16/04/2019 à 19:36, John Beard a écrit :
> Hi JP,
>
> I think the problem is that the members *within* ZONE_CONTAINER are
> uninitialised, but they are accessed by the very act of trying to set
> them from ZONE_SETTINGS::ExportSetting. If they had a spurious value
> that was the same as the new
Hi JP,
I think the problem is that the members *within* ZONE_CONTAINER are
uninitialised, but they are accessed by the very act of trying to set
them from ZONE_SETTINGS::ExportSetting. If they had a spurious value
that was the same as the new value, the refill would not happen.
The call stacks ar
Le 16/04/2019 à 17:59, John Beard a écrit :
> Hi,
>
> The following members are not initialised in ZONE_CONTAINER's
> constructor, but they are accessed in the Setter functions:
>
> * m_ThermalReliefCopperBridge
> * m_ZoneMinThickness
>
> This was picked up with valgrind memcheck:
>
> valgrind
Hi,
The following members are not initialised in ZONE_CONTAINER's
constructor, but they are accessed in the Setter functions:
* m_ThermalReliefCopperBridge
* m_ZoneMinThickness
This was picked up with valgrind memcheck:
valgrind --tool=memcheck qa/pcbnew_tools/qa_pcbnew_tools pcb_parser
/tmp/ci
4 matches
Mail list logo
