Another instruction which appears to have issues with memory operands and breakpoint on the instruction is vpmuludq. This time it didn't crash but I was looking at completely incorrect multiplication results compared to incoming values to the instruction. To me this indicates like vpmuludq read the memory operand from wrong address which happened to be a mapped address.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850258 Title: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
