Comment #4 on issue 369 by [email protected]: segfault on release build with gcc 4.1.2 p1.3 (Gentoo) http://code.google.com/p/v8/issues/detail?id=369
I strongly encourage the submitter to track down the problem, and help us fix it. It would be difficult for us to reproduce it here if it has a fragile dependence on exactly that build configuration, but we are very interested in fixing it. A first step would be to add high optimization like -O2 -g to the debug build, and you might be able to tell what function or module is causing the problem, using gdb. That is, if adding -O2 recreates the problem. Remember to keep making clean builds when making all these changes - sometimes the timestamps don't do what they should. -- 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 -~----------~----~----~----~------~----~------~--~---
