Kicad crashes on project open

[Mitja Nemec]

When moving a project folder and opening Kicad, Kicad obviously does not open a project. This is fine. But when you choose File/Open Project, the program crashes. You can open a recent project (if you have it in the list) and then open a moved project.

Using:
Application: kicad
Version: (2018-02-13 revision 365ab99a6)-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 7 (build 7601, Service Pack 1), 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

[Jeff Young (jeyjey)]

Moving the project folder and moving the .pro file both work fine on Mac. Windows-specific?

[jean-pierre charras (jp-charras)]

On W7 / 32 bits it does not crash.

[Mitja Nemec (mitjan)]

It looks like it is a computer specific. I've tried this on three different computers and it crashes on only one. So it is most likely Windows issue, and bug can probably be closed.

I am attaching a windows output message if anybody can tell anything from it:

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: kicad.exe
  Application Version: 0.0.0.0
  Application Timestamp: 00000000
  Fault Module Name: COMCTL32.dll
  Fault Module Version: 6.10.7601.17514
  Fault Module Timestamp: 4ce7c45b
  Exception Code: c0000005
  Exception Offset: 0000000000093ec4
  OS Version: 6.1.7601.2.1.0.256.4
  Locale ID: 1060
  Additional Information 1: 8948
  Additional Information 2: 8948414846d42b127eadf95e1fe340c0
  Additional Information 3: 1b6f
  Additional Information 4: 1b6f282139116471ab74abec12ca975f

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

[Mitja Nemec (mitjan)]

I've found out that gdb is packaged along nightly release.

This is a gdb output when trying to open a project and project opened the last time the KiCad was running was moved:

C:\Program Files\KiCad\bin>gdb kicad.exe
Python Exception <type 'exceptions.ImportError'> No module named gdb:
C:\Program Files\KiCad\bin\gdb.exe: warning:
Could not load the Python gdb module from `c:\mingw64\share\gdb/python'.
Limited Python support is available from the _gdb module.
Suggest passing --data-directory=/path/to/gdb/data-directory.

GNU gdb (GDB) 8.0
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kicad.exe...(no debugging symbols found)...done.
(gdb) run
Starting program: C:\Program Files\KiCad\bin\kicad.exe
[New Thread 3076.0xfb0]
[New Thread 3076.0x12ec]
[New Thread 3076.0x8f0]
[New Thread 3076.0x12dc]
[New Thread 3076.0xecc]
[New Thread 3076.0x918]
[New Thread 3076.0x1300]
[New Thread 3076.0x6a0]
[New Thread 3076.0x98c]
[New Thread 3076.0xfc0]
[New Thread 3076.0xdc0]
[New Thread 3076.0x118]

Thread 1 received signal SIGSEGV, Segmentation fault.
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
0x000007fefb623ec4 in TaskDialog ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
(gdb)

[Maciej Suminski (orsonmmz)]

Mitja, please execute 'bt' command when you get gdb prompt after the crash.

[Mitja Nemec (mitjan)]

Thanks for the patience and directions, it is my first time.

Here it is:
Reading symbols from kicad.exe...(no debugging symbols found)...done.
(gdb) run
Starting program: C:\Program Files\KiCad\bin\kicad.exe
[New Thread 3748.0x1138]
[New Thread 3748.0x1020]
[New Thread 3748.0x10a4]
[New Thread 3748.0xed8]
[New Thread 3748.0x1108]
[New Thread 3748.0x6ec]
[New Thread 3748.0xec0]
[New Thread 3748.0x1128]
[New Thread 3748.0xc68]
[New Thread 3748.0xd4c]
[New Thread 3748.0x4e0]
[New Thread 3748.0xa54]
[New Thread 3748.0x13a4]

Thread 1 received signal SIGSEGV, Segmentation fault.
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
0x000007fefb623ec4 in TaskDialog ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
(gdb) bt
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
Python Exception <type 'exceptions.ImportError'> No module named gdb.frames:
#0 0x000007fefb623ec4 in TaskDialog ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
#1 0x000007fefb623d3b in TaskDialog ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
#2 0x000007fefb6269f2 in TaskDialog ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
#3 0x000007fefb628ec3 in TaskDialog ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
#4 0x0000000076eb9bd1 in USER32!TranslateMessageEx ()
   from C:\Windows\system32\user32.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
#5 0x0000000076eb3bfc in USER32!CallWindowProcW ()
   from C:\Windows\system32\user32.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
#6 0x0000000076eb3b78 in USER32!CallWindowProcW ()
   from C:\Windows\system32\user32.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
#7 0x000007fefb5b6215 in CreateUpDownControl ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf-
--Type <return> to continue, or q <return> to quit---
1df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
Python Exception <type 'exceptions.NameError'> Installation error: gdb.execute_u
nwinders function is missing:
#8 0x000007fefb5b69a0 in DefSubclassProc ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa39...

[Wayne Stambaugh (stambaughw)]

It appears that gdb is missing some libraries and is not giving any useful information. Maybe we are not including all of the gdb python dependencies in our windows installer.

[Nick Østergaard (nickoe)]

@Wayne, yes, it is highly likely that the build is missing some things for gdb. It has not been tested much.

[Wayne Stambaugh (stambaughw)]

I would be nice if we could figure out what is missing and add it to the
installer to get a decent backtrace. The backtrace attached to this bug
report doesn't help very much.

On 3/2/2018 11:26 AM, Nick Østergaard wrote:
> @Wayne, yes, it is highly likely that the build is missing some things
> for gdb. It has not been tested much.
>

[Mitja Nemec (mitjan)]

So, I've found the time to find what I think is working version of gdb and I am attaching gdb backtrace once again

The way I see it it is most likely Windows problem or maybe a certain version of Windows dlls and Wx. So most likely it is not a Kicad issue.

I will gladly do anything else that I am capable of.

Here is the gdb output:

C:\Program Files\KiCad\bin>c:\Programs\mingw64\bin\gdb.exe kicad.exe
GNU gdb (GDB) 7.1.90.20100730-cvs
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from C:\Program Files\KiCad\bin/kicad.exe...(no debugging symbol
s found)...done.
(gdb) run
Starting program: C:\Program Files\KiCad\bin/kicad.exe
[New Thread 4528.0x264]
[New Thread 4528.0x105c]
[New Thread 4528.0x508]
[New Thread 4528.0x113c]
[New Thread 4528.0xfa4]
[New Thread 4528.0x13d4]
[New Thread 4528.0x1d8]
[New Thread 4528.0xa48]
[New Thread 4528.0x9cc]
[New Thread 4528.0xcdc]
[New Thread 4528.0x12a4]
[New Thread 4528.0xc74]
[New Thread 4528.0x1108]

Program received signal SIGSEGV, Segmentation fault.
0x000007fefba83ec4 in FlatSB_EnableScrollBar ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
(gdb) bt
#0 0x000007fefba83ec4 in FlatSB_EnableScrollBar ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
#1 0x000000000641b100 in ?? ()
#2 0x000007fefdaf3870 in ole32!CoGetObjectContext ()
   from C:\Windows\system32\ole32.dll
#3 0x000007fefdaed108 in ole32!CoGetObjectContext ()
   from C:\Windows\system32\ole32.dll
#4 0x000000000022c440 in ?? ()
#5 0x0000000000000005 in ?? ()
#6 0x0000000000000001 in ?? ()
#7 0x0000000000000005 in ?? ()
#8 0x000007fefba83d3b in FlatSB_EnableScrollBar ()
   from C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1
df_6.0.7601.17514_none_fa396087175ac9ac\comctl32.dll
#9 0x0000000005b25e20 in ?? ()
#10 0x0000000000000000 in ?? ()
(gdb)

[Wayne Stambaugh (stambaughw)]

@Mitja, there is nothing in your latest back trace to indicate that there is a bug in KiCad that fits your description. It looks like you may have a broken windows configuration. I'm tempted to set the status of this bug report to invalid unless someone else can reproduce it. Does anyone object to this proposal?

[Mitja Nemec (mitjan)]

@Wayne. Yes it most likely is a broken windows system, so as far as I am concerned you can mark this bug as invalid. I do apologize for the noise.

[Wayne Stambaugh (stambaughw)]

I changed the status to this bug report to invalid. If someone can duplicate this and provide some feedback that indicates that this is an issue with kicad, please feel free to reopen it.