[Pkg-electronics-devel] Bug#896706: pcbnew: crashes with a failed assertion on i386, starts fine on amd64

[Carsten Schoenert]

Control: severity -1 serious

Hello Mirko,

On Sat, Jun 02, 2018 at 02:41:38PM +0200, Mirko Parthey wrote:
> OK, I got kicad 5.0.0~rc2+dfsg1-2 from unstable.
> Here's a typescript of my gdb session with a backtrace.
> ...
> #26 0x0041cd2d in PGM_SINGLE_TOP::OnPgmInit (this=<optimized out>) at ./common/single_top.cpp:322
> #27 0x0042053e in APP_SINGLE_TOP::OnInit (this=0x4b2600) at ./common/single_top.cpp:128
> #28 0xb7518176 in wxEntry(int&, wchar_t**) () from /usr/lib/i386-linux-gnu/libwx_baseu-3.0.so.0
> #29 0xb7518f83 in wxEntry(int&, char**) () from /usr/lib/i386-linux-gnu/libwx_baseu-3.0.so.0
> #30 0x00419e56 in main (argc=<optimized out>, argv=0xbffff414) at ./common/single_top.cpp:239
> (gdb) quit
> A debugging session is active.

I picked up a older laptop and installed a Debian testing i386 on it and
I can reproduce that segfault here too. I also did a GDB trace of such a
segfault and forwarded it to the bug report on the upstream bug tracker.

It's now mostly up to the upstream developers to find the origin of the
segfault which we see. Could be some additional compiler flags that are
needed but also some specific platform macros that are needed.
I'm not a expert in reading GDB logs so I hope the upstream developers
can detect the issues in the logs.

I marked this report now as serious as this is a RC bug. Until it's
solved we wont see a migration of the kicad packages to testing.

Regards
Carsten