Rebased with master.
This issue could be re-produced by:
make ia32.debug gdbjit=on -j8
cd benchmarks
../out/ia32.debug/d8 ./run.js --gdbjit
Richards: 22872
DeltaBlue: 17594
Crypto: 19710
RayTrace: 6901
#
# Fatal error in ../src/gdb-jit.cc, line 2173
# CHECK(e->value == __null) failed
#
==== C stack trace ===============================
1:V8_Fatal
2:v8::internal::GDBJITInterface::RegisterDetailedLineInfo(v8::internal::Code*,v8::internal::GDBJITLineInfo*)
3:v8::internal::FullCodeGenerator::MakeCode(v8::internal::CompilationInfo*)
The gdbjit feature is very useful for the port developers and for anyone who
wants to debug the JavaScript code and C++ codes together. It will be great
that
gdbjit compilation and the "d8 ./run.js --gdbjit" could be added into the
trybots so that this feature will not be broken accidentally in the future.
https://codereview.chromium.org/13880031/
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
