Re: [Kicad-developers] [PATCH] Crash Reporter

2019-04-16 Thread Carsten Schoenert
Hello, Am 16.04.19 um 23:25 schrieb Mark Roszko: > Just to throw it out there > > Did you consider at all at using something off the shelf such as > Breakpad which both Mozilla and Chrome use? > https://wiki.mozilla.org/Breakpad  > https://github.com/google/breakpad this has also some downsides.

Re: [Kicad-developers] Test failures

2019-04-16 Thread Seth Hillbrand
Am 2019-04-16 21:52, schrieb Simon Richter: Hi, Jenkins reports test failures for commit 8cc3c6f15 "Prevent iteration over empty polygon": Should be fixed. Thanks Simon! ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-

[Kicad-developers] Test failures

2019-04-16 Thread Simon Richter
Hi, Jenkins reports test failures for commit 8cc3c6f15 "Prevent iteration over empty polygon": Running 67 test cases... /var/lib/jenkins/workspace/linux-kicad-head/src/qa/common/geometry/test_shape_poly_set_collision.cpp(179): error: in "SPSCollision/CollideVertex": check common.holeyPolySet.Coll

Re: [Kicad-developers] [PATCH] Crash Reporter

2019-04-16 Thread Tomasz Wlostowski
On 16/04/2019 23:25, Mark Roszko wrote: > Just to throw it out there > > Did you consider at all at using something off the shelf such as > Breakpad which both Mozilla and Chrome use? > https://wiki.mozilla.org/Breakpad  > https://github.com/google/breakpad Hi Mark, I took some inspiration from

Re: [Kicad-developers] [PATCH] Crash Reporter

2019-04-16 Thread Tomasz Wlostowski
On 16/04/2019 22:52, Seth Hillbrand wrote: > Am 2019-04-14 18:50, schrieb Tomasz Wlostowski: >> Dear all, >> >> The attached patchset introduces a builtin crash reporter for Kicad - >> that is a window that pops up in case of a segmentation fault/other >> serious error, kindly apologizes to the use

Re: [Kicad-developers] [PATCH] Crash Reporter

2019-04-16 Thread Mark Roszko
Just to throw it out there Did you consider at all at using something off the shelf such as Breakpad which both Mozilla and Chrome use? https://wiki.mozilla.org/Breakpad https://github.com/google/breakpad There's then some off the shelf software potentially for processing Breakpad reports such as

Re: [Kicad-developers] [PATCH] Crash Reporter

2019-04-16 Thread Wayne Stambaugh
Tom, On 4/16/19 4:52 PM, Seth Hillbrand wrote: > Am 2019-04-14 18:50, schrieb Tomasz Wlostowski: >> Dear all, >> >> The attached patchset introduces a builtin crash reporter for Kicad - >> that is a window that pops up in case of a segmentation fault/other >> serious error, kindly apologizes to th

Re: [Kicad-developers] [PATCH] Crash Reporter

2019-04-16 Thread Seth Hillbrand
Am 2019-04-14 18:50, schrieb Tomasz Wlostowski: Dear all, The attached patchset introduces a builtin crash reporter for Kicad - that is a window that pops up in case of a segmentation fault/other serious error, kindly apologizes to the user and lets him/her submit (anonymously) a bug report to u

Re: [Kicad-developers] Uninitialised ZONE_CONTAINER members

2019-04-16 Thread jp charras
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

Re: [Kicad-developers] Uninitialised ZONE_CONTAINER members

2019-04-16 Thread John Beard
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

Re: [Kicad-developers] Uninitialised ZONE_CONTAINER members

2019-04-16 Thread jp charras
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

[Kicad-developers] Uninitialised ZONE_CONTAINER members

2019-04-16 Thread John Beard
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

Re: [Kicad-developers] Zoom & Grid changes

2019-04-16 Thread Jeff Young
Click-to-place tools moved to modern toolset. (Place component, no-connect, junction, wire-to-bus, bus-to-bus, label, hierarchical-label, global-label, text and image.) > On 14 Apr 2019, at 12:13, Jeff Young wrote: > > Net highlight tool now moved to modern toolset. > > >> On 13 Apr 2019, at

Re: [Kicad-developers] Monster files wanted

2019-04-16 Thread easyw
Hi, please have a look at this board (12 layers) https://github.com/ciaa/Hardware/blob/master/PCB/ACC/CIAA_ACC/ciaa_acc.kicad_pcb this is from 'Made with KiCAD' section. M On 04/16/2019 11:27 AM, John Beard wrote: Hi, Occasionally, there are references made to performance during processing of

Re: [Kicad-developers] Monster files wanted

2019-04-16 Thread Andrew Lutsenko
Hi John, Here are some big examples that I test my plugin on: https://github.com/OLIMEX/DIY-LAPTOP/tree/master/HARDWARE/A64-TERES/TERES-PCB1-A64-MAIN/Rev.C https://github.com/c4puter/motherboard https://github.com/rusefi/rusefi/tree/master/hardware/frankenso Regards, Andrew On Tue, Apr 16, 2019

[Kicad-developers] Monster files wanted

2019-04-16 Thread John Beard
Hi, Occasionally, there are references made to performance during processing of very large >8 layer PCBs (and the schematics thereof). However, I don't have any such PCBs to uses as a reference, and there are (reasonably, due to the size) none in the demos folder. I can make faked-up PCBs program