Comment #5 on issue 369 by coldredlemur: segfault on release build with gcc
4.1.2 p1.3 (Gentoo)
http://code.google.com/p/v8/issues/detail?id=369
Compiling in debug mode with -O2 allows me to inspect the backtraces of the
failed
tests. They always look like this:
#3 0x081a9f5b in v8::internal::OS::Abort () at src/platform-linux.cc:172
#4 0x0807e68a in V8_Fatal (file=0x8289b2e "src/handles-inl.h", line=49,
format=0x8289a96 "CHECK(%s) failed")
at src/checks.cc:56
#5 0x08076e93 in v8::internal::Genesis::BuildSpecialFunctionTable
(this=0xbfd64334) at
src/checks.h:62
#6 0x08078760 in Genesis (this=0xbfd64334, global_object={location_ = 0x0},
global_template=
{val_ = 0x830a9bc}, extensions=0x0) at src/bootstrapper.cc:1546
#7 0x0807883f in v8::internal::Bootstrapper::CreateEnvironment
(global_object={location_ = 0x0},
global_template={val_ = 0x830a9bc}, extensions=0x0) at
src/bootstrapper.cc:352
#8 0x0805b259 in v8::Context::New (extensions=0x0, global_template={val_ =
0x830a988},
global_object=
{val_ = 0x0}) at src/api.cc:2541
#9 0x0804a9ba in RunMain (argc=2, argv=0xbfd64554) at samples/shell.cc:66
#10 0x0804acc7 in main (argc=Cannot access memory at address 0x4236
) at samples/shell.cc:107
Not knowing what any of this is, I looked at the blame for
BuildSpecialFunctionTable,
found the relevant revisions are 1886 and 1888 - but the tests do not work
for me in
1885. So those must not be the problem.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
-~----------~----~----~----~------~----~------~--~---
