I would step through Genesis::BuildSpecialFunctionTable (bootstrapper.cc:1499)The reason the debug trace isn't showing a line in that function is probably because functions called by it are inlined, including the CheckHelper function called by the CHECK macro. By stepping through, and perhaps stepping in one level to the called functions, you should be able to pin down where in the changed code something goes wrong.
On Wed, Jun 3, 2009 at 8:06 PM, <[email protected]> wrote: > > > Comment #8 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 > > Great work. 1539 is http://codereview.chromium.org/49001 which makes a > lot > of sense > if it's a compiler bug. > > -- > 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 > > > > -- William Hesse Software Engineer [email protected] Google Denmark ApS Frederiksborggade 20B, 1 sal 1360 København K Denmark CVR nr. 28 86 69 84 If you received this communication by mistake, please don't forward it to anyone else (it may contain confidential or privileged information), please erase all copies of it, including all attachments, and please let the sender know it went to the wrong person. Thanks. --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
