Hi,
On Mon, Aug 06, 2018 at 05:07:56PM -0700, Seth Hillbrand wrote:
> Hello Carsten and Werner-
>
> I've committed a potential fix to this issue to the kicad tree (
> https://git.launchpad.net/kicad/commit/?id=edbf34c2b2965f63537e485d958f00166f01bc5a).
> However, it has only been seen to correct
Hello Carsten and Werner-
I've committed a potential fix to this issue to the kicad tree (
https://git.launchpad.net/kicad/commit/?id=edbf34c2b2965f63537e485d958f00166f01bc5a).
However, it has only been seen to correct the similar behavior we observed
earlier and I have been unable to recreate
Hello Carsten,
Thank you very much for your efforts.
As far as I understand the situation, this is not a segfault, but an intended
abort caused by a failed assertion.
Here is the GDB log:
$ gdb pcbnew
GNU gdb
Hello Werner,
On Wed, Aug 01, 2018 at 05:11:40PM +0200, Werner Frey wrote:
...
> pcbnew aborts immediately after invocation on my i386 Debian Buster
> installation.
> The kicad package was freshly installed for the first time.
> There were no changes to the default configuration of the package.
Package: kicad
Version: 5.0.0+dfsg1-1
Severity: important
Tags: upstream
Dear Maintainer,
pcbnew aborts immediately after invocation on my i386 Debian Buster
installation.
The kicad package was freshly installed for the first time.
There were no changes to the default configuration of the
5 matches
Mail list logo
