https://bugs.kde.org/show_bug.cgi?id=466172
--- Comment #7 from Paul Floyd <pjfl...@wanadoo.fr> --- (In reply to Mike J from comment #6) > Thanks Paul. I was unaware of TUI mode, its really useful. > > The following extract is from the TUI asm and command windows. > It shows a int3 rather than a push %rbp on the initial entry, where the call > stack still shows as being normal. > On the stepi (rather than a step tried previously), the call stack has then > become corrupted. > > Is the int3 likely to be something that valgrind might introduce instead of > the push %rbp ? int3 causes the application to stop if it is being debugged or (as the title of this item says) terminate with SIGTRAP. Valgrind doesn't use PTRACE like debuggers do, and it shouldn't be inserting an int3 since it will still cause a SIGTRAP. I don't yet have any ideas what could cause the memory to be corrupted. -- You are receiving this mail because: You are watching all bug changes.
