Maciej

I made a debug build and ran it using debug as you suggested. Unfortunately, as of this build I cannot replicate the bug. The good news is I now know what to do if it appears again. It was absolutely consistent in the past.

Brian

Application: kicad
Version: (5.0.0-rc2-dev-269-gff3f22987), debug 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
    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=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_SPICE=ON

-----Original Message-----
From: <email address hidden> <email address hidden> On Behalf Of Maciej Suminski
Sent: March 22, 2018 11:15 AM
To: <email address hidden>
Subject: [Bug 1747546] Re: Fatal crash eeSchema V5 assigning footprint

If you managed to reproduce the problem reliably and now it stops, then I will be even happier to hear that.

I assume you have followed "Building using MSYS2" paragraph in the official documentation. If so, you will need to create another subdirectory in the source directory and rerun the cmake line replacing "-DCMAKE_BUILD_TYPE=Release" with "-DCMAKE_BUILD_TYPE=Debug", followed by the usual make and make install commands. You will also need to install gdb itself ('pacman -S mingw-w64-x86_64-gdb' command in the
msys2 shell).

Once it is done, you will get a KiCad build with debug symbols. The next step is to run KiCad with gdb (simply launch 'gdb kicad' in the msys2 shell). In the gdb command prompt you need to execute 'run' command to actually start KiCad. Once you manage to crash it, type 'bt' in the gdb shell and post it here.

Many thanks for your cooperation, please let me know if any of the instructions is not clear.

1. http://docs.kicad-
pcb.org/doxygen/md_Documentation_development_compiling.html

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1747546

Title:
  Fatal crash eeSchema V5 assigning footprint

Status in KiCad:
  New

Bug description:
  Application: kicad
  Version: (2018-01-26 revision 54ebd4574)-makepkg, release build
  Libraries:
      wxWidgets 3.0.3
      libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
  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.60.0
      Curl: 7.54.1
      Compiler: GCC 7.1.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_SPICE=ON

  When editing a specific component (resistor) to assign a footprint, if
  I browse footprints, select R_1206 handsoldering and double click or
  select "Insert Footprint in board" the footprint browser would crash
  and throw error "Error unmapping vertices buffer:invalid operation".

  After this, the browser would hang and all KiCad windows would no
  longer function until all were killed via Task Manager.

  This happened eveyr time I tried it until I decided to use CVPCB to
  assign the footprint. After that the error was thrown once then
  disappeared and even new parts would not cause a problem.

  This was a file imported from V4 if that matters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kicad/+bug/1747546/+subscriptions