[Kicad-developers] Two bugs reported on the Fedora bugzilla

2022-05-06 Thread Steven A. Falco
There are two SIGABRT bugs reported on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2079984 https://bugzilla.redhat.com/show_bug.cgi?id=2082394 The first bug was closed because it was not able to be reproduced. The second one has apparently happened to the reporter several times, but a

Re: [Kicad-developers] Two bugs reported on the Fedora bugzilla

2022-05-06 Thread Seth Hillbrand
Hi Steven- The second bug is locked down. We can't see it without proper access credentials. Seth On Fri, May 6, 2022 at 6:45 AM Steven A. Falco wrote: > There are two SIGABRT bugs reported on Fedora: > > https://bugzilla.redhat.com/show_bug.cgi?id=2079984 > > https://bugzilla.redhat.com/show

Re: [Kicad-developers] Two bugs reported on the Fedora bugzilla

2022-05-06 Thread Ian McInerney
The second bug appears to be an assertion due to an invalid vector access. The stack trace is below. Truncated backtrace: Thread no. 1 (10 frames) #2 std::__replacement_assert at /usr/include/c++/11/x86_64-redhat-linux/bits/c++config.h:2660 #3 std::vector, std::allocator > >::operator[] at /usr

Re: [Kicad-developers] Two bugs reported on the Fedora bugzilla

2022-05-06 Thread Seth Hillbrand
Ah, thanks! Looks like that was fixed in master but didn't get cherry-picked. The fix is in the v6 branch now. Seth On Fri, May 6, 2022 at 11:08 AM Ian McInerney wrote: > The second bug appears to be an assertion due to an invalid vector access. > > The stack trace is below. > > Truncated bac

Re: [Kicad-developers] Two bugs reported on the Fedora bugzilla

2022-05-06 Thread Steven A. Falco
Sorry about the bug being private. I've changed it to be public. Regarding the cherry pick - I see commit 485e89f7a5, and I'll try to apply it as a patch on top of 6.0.5. Steve On 5/6/22 02:54 PM, Seth Hillbrand wrote: Ah, thanks! Looks like that was fixed in master but didn't get c