https://bugs.kde.org/show_bug.cgi?id=417187
--- Comment #17 from Stefan Maksimovic <stefan.maksimo...@rt-rk.com> --- Created attachment 126749 --> https://bugs.kde.org/attachment.cgi?id=126749&action=edit handle branches in delay slots We've taken a second look at the possible scenarios you described and updated the current changes so as to cover the special cases which could have possibly caused disInstr_MIPS_WRK to go into an arbitrarily deep recursion. The result is that valgrind now mimics the behaviour of a program by emitting a SIGILL in cases where the program ran by itself also does. Tested it on a contrived example (by having consecutive branches in the delay slots of those above) and managed to get a matching behaviour between valgrind and a standalone run of the example. -- You are receiving this mail because: You are watching all bug changes.
