https://bugs.kde.org/show_bug.cgi?id=503813
--- Comment #22 from Igor Kushnir <igor...@gmail.com> --- (In reply to ulterno from comment #21) > Unless the guard is supposed to be somewhere else, that I haven't realised. No, your debugging code looks good now. > For now, all the times I have tried (with minor variations here and there), > there has been no case where I prevented a crash after getting: > kdevplatform.shell: populateContextMenu() called while we still handled > another menu. Where does it crash now? (check the backtrace). Maybe another similar fix is needed elsewhere... I suspect that a bug in Qt Creator prevents you from debugging KDevelop in it. So I suggested the GDB command line or the KDevelop debugger UI, which might work. I regularly debug KDevelop in KDevelop. Another thing you could try is create a small Qt application and see if two menus are created in it too when the Menu key is pressed. Then you could report a Qt bug with the minimum reproducible example attached. By the way, have you verified that only one menu is created when you right-click instead of pressing the Menu key? -- You are receiving this mail because: You are watching all bug changes.
