kicad-developers team mailing list archive

["Steven A. Falco" <stevenfalco@xxxxxxxxx>]

I'll add a comment to the bug, and see if the user can reproduce the problem.  I'll suggest hitting "down arrow".

	Steve

On 3/31/19 11:12 AM, Jon Evans wrote:
> Looks like this happened inside the component selector when the users pressed the down arrow key.
> 
> I think the stack trace is assuming one of the wx GetNextItem calls instead of the one in wxdataviewctrl_helpers.cpp which is what was actually called (I think?)
> 
> Without an accurate backtrace inside GetNextItem it's hard to guess exactly what went wrong.
> 
> -Jon
> 
> On Sun, Mar 31, 2019 at 9:28 AM Steven A. Falco <stevenfalco@xxxxxxxxx <mailto:stevenfalco@xxxxxxxxx>> wrote:
> 
>     I was alerted to the following bug report:
> 
>     https://bugzilla.redhat.com/show_bug.cgi?id=1694288
> 
>     The user hit a key - doesn't know which key - and somehow triggered a crash in GetNextItem.  I don't know if this bug report is helpful, but it does have a backtrace, and we know which version of KiCad it applies to (1:kicad-5.0.2-5.fc29) so it should be possible to correlate the backtrace to the source code.
> 
>     I don't know if the user saved the schematic, or if the crash is reproducible, but I can ask for more info if anyone thinks this is worth pursuing.
> 
>             Steve
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     More help   : https://help.launchpad.net/ListHelp
>