mikhail.naganov@gmail.com 0fcedde224 Fix determining of JS lower stack bottom used in profiler's JS stack tracer to work with Chromium. ... My assumption that log initialization happens somewhere near the stack's bottom is true for V8's sample shell but isn't true for Chromium, causing many otherwise valid stack addresses to be thrown out. The solution proposed is to save stack pointer value for the outermost JS function in ThreadLocalTop similar to c_entry_fp. Implemented only for IA-32. Currently I'm not dealing with profiling on ARM and x86-64 anyway. Review URL: http://codereview.chromium.org/112082 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2086 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2009-06-02 09:33:17 +00:00
..
cctest	Fix determining of JS lower stack bottom used in profiler's JS stack tracer to work with Chromium.	2009-06-02 09:33:17 +00:00
message	Fixed a bunch of memory leaks in tests, including:	2009-03-27 00:24:49 +00:00
mjsunit	Added stack overflow check for RegExp analysis phase.	2009-05-27 11:23:26 +00:00
mozilla	Add support for \b and ^ and $ in multiline mode, completing Irregexp	2009-01-19 18:56:47 +00:00