Fixed segmentation fault that could happen under rare conditions with handlers chaining speedups enabled.
I saw that issue under gcc 4.9.0. for some reason gcc 4.9.0 didn't optimize next handler call in all fpu opcode handlers.
As result, instead of finishing the handler and jumping to next one, the next handler is called blowing up stack.
After some long period stack overflow might occur.

The fix simply limit the max chaining depth to 1000 traces (should be enough)
The same fix should be able to address the stack overflow problem when compiling with -O0 and handlers chaining speedup enabled.


git-svn-id: svn://svn.code.sf.net/p/bochs/code/trunk@12509 6c8e4198-a580-4521-a02f-c9ae86df1db9