Comment #2 on issue 369 by erik.corry: segfault on release build with gcc 4.1.2 p1.3 (Gentoo) http://code.google.com/p/v8/issues/detail?id=369
You can disregard the two test failures. They are just timeouts caused by things running slower without optimization. You can add timeout=300 to make them go away. Since the problem seems to be optimization there are two ways to try to pin down the problem and you may need both. One is to find the revision with the problem by using binary search and cvs up -rxxxx to switch between revisions. When you have the revision that introduced the problem (assuming you can find that) if it's a big change you will have to compile some files with -O0 and some with -O2 to find out which file is causing the problem. I think you can see the link-command scons uses and replicate that with a mixture of .o files with and without optimization until you find the one that is causing the trouble. -- 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 -~----------~----~----~----~------~----~------~--~---
