giseldo/neodataset huggingface dataset:
Pcbnew: incorrect DXF arc import (lp:#1792413)

[Original report](https://bugs.launchpad.net/bugs/1792413) created by **Wayne Stambaugh (stambaughw)**
```
It appears the latest DXF arc import has been broken with the new DXF
library.  See the attached screenshot of the bad import.  The included
sample DXF file opens correctly in both FreeCAD and DraftSight so I'm going
to assume Pcbnew is the issue.

Application: kicad
Version: (6.0.0-rc1-dev-495-gab9288235-dirty), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.0.2p (WinSSL) zlib/1.2.11 brotli/1.0.5
libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.33.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```

Story points: 6.0
saving a footprint opened from a board has usability problems (lp:#1792256)

[Original report](https://bugs.launchpad.net/bugs/1792256) created by **eelik (eelik)**
```
There are usability problems with the new Footprint Library Editor when a
footprint is opened from a board to be edited. First, the editor seems to
select the original library's footprint in the tree view. That's misleading
because that's not the footprint which is under work. Then there's the save
action which normally saves the opened footprint to the file which is
selected in the tree view. But now it doesn't do that, it saves to the
board from which the footprint was opened, which is inconsistent. And
lastly it's not obvious that you can save the footprint to the board at all
because there's no hint about that kind of action anywhere. The tool button
which was still in v5.0 isn't there anymore, and even the tooltip of the
Save button says it saves to the active library, which isn't true.
```
Original tags: pcbnew

Story points: 12.0
changed footprint name isn't reflected in the tree (lp:#1792243)

[Original report](https://bugs.launchpad.net/bugs/1792243) created by **eelik (eelik)**
```
If I change the footprint name in Footprint Library Editor's "Footprint
properties" nothing seems to happen. Actually the footprint exists with the
new name, but it's visible in the tree view only after closing and
reopening the editor, even if it is saved after renaming. The most logical
behavior would be to actually change the name without copying the
footprint. Copying with a new name would be OK (and safe) but it should be
visible in the tree view immediately and it should then be the active
footprint.
```
Original tags: pcbnew

Story points: 6.0
Pcbnew: Incorrect net count (lp:#1792235)

[Original report](https://bugs.launchpad.net/bugs/1792235) created by **Fabián Inostroza (fabianinostroza)**
```
Create an empty project and open Pcbnew, the net count at the bottom shows
1 net but there is none.

Application: kicad
Version: (6.0.0-rc1-dev-484-g9b50b9406), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 GnuTLS/3.5.19 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.32.0 librtmp/2.3
Platform: Linux 4.17.0-3-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 6.0
Pcbnew: Measure tool leaves unwanted text (lp:#1792232)

[Original report](https://bugs.launchpad.net/bugs/1792232) created by **Fabián Inostroza (fabianinostroza)**
```
See the attached video

Application: kicad
Version: (6.0.0-rc1-dev-484-g9b50b9406), debug build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 GnuTLS/3.5.19 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.32.0 librtmp/2.3
Platform: Linux 4.17.0-3-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 14.0
can't use "save as" properly with modified footprint (lp:#1792207)

[Original report](https://bugs.launchpad.net/bugs/1792207) created by **eelik (eelik)**
```
With the new footprint editor with "Libraries" tree view "Save As" doesn't
work as expected. If I modify an existing footprint I expect to be able to
save it with a new name and possibly to a new location, just like any other
software works. But Save As in File menu saves the old original unmodified
footprint. So does "Save a Copy As" in the context menu. So, all
modifications seem to be lost if I don't want to replace the old footprint,
i.e. use "Save". It's even impossible if I have modified a footprint from
write protected location.

BTW, why in the first place there are two different functions, "Save As"
and "Save a Copy As", one in the File menu and one in the context menu? I
understand the difference between them but they should both be in both
menus IMO, or alternatively only "Save As" function.

Application: kicad
Version: (6.0.0-rc1-dev-480-gf5de8cd3e), debug build
Libraries:
    wxWidgets 3.0.3
Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Compiler: GCC 7.2.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=OFF
    KICAD_USE_OCE=OFF
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```
Original tags: pcbnew

Story points: 6.0
Windows compile failure: 'GetCursorRow': is not a member of 'wxGrid' (lp:#1792196)

[Original report](https://bugs.launchpad.net/bugs/1792196) created by **Simon Richter (sjr)**
```
The MSVC build failed to compile:

    common\grid_tricks.cpp(162): error C2039: 'GetCursorRow': is not a
member of 'wxGrid'
    common\grid_tricks.cpp(162): error C2039: 'GetCursorColumn': is not a
member of 'wxGrid'
    common\grid_tricks.cpp(162): error C2660: 'wxGrid::GetCellEditor':
function does not take 1 arguments

I think I've seen similar messages earlier, IIRC these functions are
deprecated on GTK and don't exist on MSW.
```

Story points: 6.0
3d Viewer Arrow Keys (lp:#1792171)

[Original report](https://bugs.launchpad.net/bugs/1792171) created by **Leandro Heck (leoheck)**
```
Arrow keys move the 3D model in a counter-intuitive way (for me). They are
moving the object on the screen and not the camera as usual.

It is always a pain to place the spot I want to observe in the center of
the screen.

Is it possible, at least, to add an option to change this behavior?
```

Story points: 6.0
hotkeys and tooltips (lp:#1792159)

[Original report](https://bugs.launchpad.net/bugs/1792159) created by **staviq (staviq)**
```
This is a feature request.



UI Button tooltips need to:
- Contain it's hotkey in the tooltip
- Have the same description in the tooltip, in the hotkey list, and the
menu.



Current: https://i.imgur.com/LvKs3AF.png
Proposed: https://i.imgur.com/3DnTbIW.png

Proposed change does not influence the workflow of experienced users, it
would however, be immensely helpful to all the newcomers, like me.



Currently, the tooltips in the ui don't even have the same names /
descriptions as in the hotkey list or the menu. This is really confusing
for someone trying to learn Kicad.

example:
    tooltip "Route tracks", hotkey description: "Add new track"
  or
    tooltip "Add filled zones", menu item name "Place/Zone"



I believe this is very important feature missing from the project, even
though it seems like something trivial.
```
Original tags: feature.request hotkeys

Story points: 32.0
symbol editor can't handle large amount of clarification menu items (lp:#1792146)

[Original report](https://bugs.launchpad.net/bugs/1792146) created by **eelik (eelik)**
```
I used symbol editor's pin table to add pins, 14 of them at the moment. I
wanted to move them by dragging with mouse. But originally they are located
in the same place and the selection clarification menu can't handle too
many items. The latest code from launchpad git throws failed assertion:

kicad/eeschema/lib_edit_frame.cpp(1272): assert
"m_collectedItems.GetCount() <= MAX_SELECT_ITEM_IDS" failed in
locateItem(): Select item clarification context menu size limit exceeded.

It's possible that this happens for other clarification menus, too, maybe
also in pcbnew, but I haven't tested.

There really should be no upper limit or it should be very large. One
possible GUI solution would be to create hierarchical menus, like

a
b
c
d
e
f
more>
   g
   h
   i
   j
   k
   l
   more>
       etc.

Or open a dialog which could handle all items in a scrollable list.

Application: kicad
Version: (6.0.0-rc1-dev-480-gf5de8cd3e), debug build
Libraries:
    wxWidgets 3.0.3
Platform: Linux 4.13.0-46-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Compiler: GCC 7.2.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=OFF
    KICAD_USE_OCE=OFF
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```
Original tags: eeschema

Story points: 6.0
pcbnew: selecting a microwave tool cases view to scroll when "Pan while moving objects" is enabled (lp:#1792128)

[Original report](https://bugs.launchpad.net/bugs/1792128) created by **Eugeniy Meshcheryakov (eugen-debian)**
```
To reproduce:

1. Open PCB new, ensure "Pan while moving object" option is enabled.
2. Place a line using the tool from the microwave tool bar. This should
work fine.
3. Cancel tool.
4. Click on the line tool in microwave tool bar and move the mouse pointer
to the PCB area.

In my experience the view starts to scroll, even when drawing is not
started yet. With version from git, sometimes it continues to scroll wildly
even when mouse pointer is stopped. Cross hair sometimes stops following
the mouse cursor. This does not seem to happen with normal (non-microwave)
tools.

Additionally, cursor is not allowed to leave the PCB view (version 5.0.0,
only via left and top edges with git version) even when panning option is
disabled. This is rather annoying and also is not how normal tools behave
(even with scrolling enabled).

Version info, 5.0.0 from Debian unstable:

Application: kicad
Version: 5.0.0+dfsg1-2, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.33.0 librtmp/2.3
Platform: Linux 4.18.0-1-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF

Version info, custom build from git on Debian unstable:

Application: kicad
Version: (6.0.0-rc1-dev-480-gf5de8cd3e), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.33.0 librtmp/2.3
Platform: Linux 4.18.0-1-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 6.0
The about window looks broken when built with GTK3 (lp:#1792121)

[Original report](https://bugs.launchpad.net/bugs/1792121) created by **Eugeniy Meshcheryakov (eugen-debian)**
```
The about window is missing all text formatting in the current git version.
5.0.0's about window looks fine. This is with custom build on Debian
unstable. See attached screenshot.

Application: kicad
Version: (6.0.0-rc1-dev-480-gf5de8cd3e), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.33.0 librtmp/2.3
Platform: Linux 4.18.0-1-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 6.0
pcbnew: microwave line tool creates non-smooth lines (lp:#1792119)

[Original report](https://bugs.launchpad.net/bugs/1792119) created by **Eugeniy Meshcheryakov (eugen-debian)**
```
I'm trying to use the line tool from the microwave tool bar. It seems to
work fine when one specifies length that is much larger than the distance
between ends. The line looks broken when one accepts default length or
specifies one that is only slightly larger than the distance between end
points. See the attached screenshot.

Kicad version (from Debian unstable):

Application: kicad
Version: 5.0.0+dfsg1-2, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.33.0 librtmp/2.3
Platform: Linux 4.18.0-1-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF

This bug is also reproducible with current git master:

Application: kicad
Version: (6.0.0-rc1-dev-480-gf5de8cd3e), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.0 OpenSSL/1.1.1 zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2
(+libidn2/2.0.4) libssh2/1.8.0 nghttp2/1.33.0 librtmp/2.3
Platform: Linux 4.18.0-1-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
    Boost: 1.62.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.0
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=OFF
```

Story points: 12.0
[KICAD Nightly] Configure paths (lp:#1792096)

[Original report](https://bugs.launchpad.net/bugs/1792096) created by **Jorge Neiva (jo-joven)**
```
Hi

I have formatted recently and did a fresh install of Kicad Nightly.
When go to "Configure Paths" and configure the new folders path and click
"OK", the window don't close and don't save the new path.

My verison is:

Application: kicad
Version: 6.0.0-rc1-unknown-4a57541~84~ubuntu18.04.1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1
(+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
Platform: Linux 4.15.0-34-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.65.1
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.58.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

I don't know if it have been reported.

Best regards
```

Story points: 6.0
"change current footprint (xxx)" should be the default option (lp:#1792070)

[Original report](https://bugs.launchpad.net/bugs/1792070) created by **Oleg Endo (oleg.endo)**
```
When changing a footprint in pcbnew, at the moment the default option in
the dialog is "change footprints with identifier".  This will usually
change all parts with the same footprint on the board.

I don't think it's a common thing to change all footprints.  I think it's
better to have the default option in the dialog set to "change current
footprint".  It makes somewhat more sense, because clicking on a part
(selecting it), then editing any property usually edits only the selected
part.  Everything else is additional extra functionality.
```

Story points: 6.0
Design Rules dialog unit mixing (lp:#1792066)

[Original report](https://bugs.launchpad.net/bugs/1792066) created by **Jan Brittenson (bson)**
```
This is not a crash or apparent malfunction per se, just a subtle change in
how track sizes and other dimension values are parsed in the Design Rules
setup dialog in PCBNew.

Most houses mix units in mil and mm.  I use to be able to set the units to
mm, then open the dialog and enter mils as e.g. 0.008" for 8mil.  It would
parse it and convert it to mm.  This no longer works in 5.0.0 (release
version as I haven't hopped on the nightlies yet).  It's on OSX; no easy
way for me to check other platforms.

As a result I need to either sit with a calculator, or python in a
terminal, and manually convert mils to mm.  Or constantly close and reopen
the dialog and keep changing the units as I go down the spec list.   Either
is more tedious and error prone than it used to be in v4...  And I also
think software that either needs you to sit with a note pad or a calculator
to effectively use it has design issues!  I think this is a significant UI
regression.
```

Story points: 6.0
Crash on track vs keepout area DRC (lp:#1791965)

[Original report](https://bugs.launchpad.net/bugs/1791965) created by **Andrzej Wolski (awolski)**
```
Attached board (containing only track segment and keepout area) causes
pcbnew crash when running DRC.

Backtrace:

#0  0x00007fffe8f0f14a in std::vector<SHAPE_LINE_CHAIN,
std::allocator<SHAPE_LINE_CHAIN> >::operator[](unsigned long) const
(this=0x0, __n=0) at /usr/include/c++/7/bits/stl_vector.h:816
#1  0x00007fffe97eb90e in SHAPE_POLY_SET::containsSingle(VECTOR2<int>
const&, int, bool) const (this=
    0x555556b14d88, aP=..., aSubpolyIndex=0, aIgnoreHoles=false)
    at /home/user/Documents/kicad/common/geometry/shape_poly_set.cpp:1474
#2  0x00007fffe97ebedf in SHAPE_POLY_SET::DistanceToPolygon(VECTOR2<int>,
int) (this=0x555556b14d88, aPoint=..., aPolygonIndex=0) at
/home/user/Documents/kicad/common/geometry/shape_poly_set.cpp:1563
#3  0x00007fffe97ec197 in SHAPE_POLY_SET::Distance(VECTOR2<int>)
(this=0x555556b14d88, aPoint=...)
    at /home/user/Documents/kicad/common/geometry/shape_poly_set.cpp:1621
#4  0x00007fffe8f99867 in DRC::newMarker(TRACK*, ZONE_CONTAINER*, int)
(this=0x555557cae870, aTrack=
    0x55555a21c5c0, aConflictZone=0x555556b14cc0, aErrorCode=39)
    at /home/user/Documents/kicad/pcbnew/drc_marker_functions.cpp:63
#5  0x00007fffe8f8a5be in DRC::testKeepoutAreas() (this=0x555557cae870)
    at /home/user/Documents/kicad/pcbnew/drc.cpp:931
#6  0x00007fffe8f87d17 in DRC::RunTests(wxTextCtrl*) (this=0x555557cae870,
aMessages=0x55555962d000)
    at /home/user/Documents/kicad/pcbnew/drc.cpp:486

Note: this bug does not affect 5.0

Application: pcbnew
Version: (6.0.0-rc1-dev-478-gc120ae9e9), release build
Libraries:
    wxWidgets 3.0.3
    libcurl/7.57.0 OpenSSL/1.0.2n (WinSSL) zlib/1.2.11 libidn2/2.0.4
libssh2/1.8.0 nghttp2/1.29.0
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian,
wxMSW
Build Info:
    wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.66.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.57.0
    Compiler: GCC 7.3.0 with C++ ABI 1011

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=OFF
    KICAD_SCRIPTING_MODULES=OFF
    KICAD_SCRIPTING_WXPYTHON=OFF
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON
```
Original tags: pcbnew

Story points: 6.0