This entirely depends on the type and number of parameters that are passed.
Rule of thumb: as soon as a 64bit parameter appears in the call, it is likely that this code will do the wrong thing. Depending on the use of the parameters, effects could range from nothing to complete crash, with memory corruption in between. Hint: It probably wouldn't be too hard to turn this bug into an attack vector. But who really cares about security when such a bug is being ignored, despite having been identified four months ago, with a proper fix submitted for all of that time... Cheers, Marc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1398898 Title: [armhf] segfaults when trying to save a file To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1398898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs