So the original report is due to a null pointer problem. %edx is zero so (%edx) is sure to cause problems.
Perhaps valgrind is in order, but being a hard to repeat bug..... might be a little annoying.
Anyone want to try:
valgrind --trace-children=yes --tool=memcheck firefox
??
(I have no idea if this will be useful).
So the original report is due to a null pointer problem. %edx is zero so (%edx) is sure to cause problems.
Perhaps valgrind is in order, but being a hard to repeat bug..... might be a little annoying.
Anyone want to try:
valgrind --trace- children= yes --tool=memcheck firefox
??
(I have no idea if this will be useful).