Joel Dice 886dd184aa fix incorrect stack unwinding for asynchronous stack traces
Our Thread.getStackTrace implementation is tricky because it might be
invoked on a thread executing arbitrary native or Java code, and there
are numerous edge cases to consider.  Unsurprisingly, there were a few
lingering, non-fatal bugs revealed by Valgrind recently, one involving
the brief interval just before and after returning from invokeNative,
and the other involving an off-by-one error in x86.cpp's nextFrame
implementation.  This commit fixes both.
2012-06-18 14:27:18 +00:00
..
2012-06-06 12:58:24 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2011-11-07 17:14:41 -07:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2010-12-05 20:21:09 -07:00
2012-06-02 15:43:42 -06:00
2012-06-02 15:43:42 -06:00
2012-05-11 17:43:27 -06:00
2011-02-26 12:45:22 -07:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2010-12-05 20:21:09 -07:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00
2012-05-11 17:43:27 -06:00