https://bugs.kde.org/show_bug.cgi?id=375971
--- Comment #10 from Martin Gräßlin <mgraess...@kde.org> --- > It is the same process, still running until now if you want something, > maybe > different timing can cause different gdb output :) sure, sure. But if we have 100 % cpu usage cases, it's quite often, that gdb ends in the same area. Which is why I was interested in gdb in the first place. I just hoped, that it ends up always in the same spot - that would make investigating easier. -- You are receiving this mail because: You are watching all bug changes.
