140508 2015-01-15 13:22:22 -0800 Some console messages erroneously skip the first ScriptCallStack frame when computing source locations 2017-01-18 23:39:31 -0800 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Unspecified Unspecified NEW P2 Normal --- 140478 1 burg webkit-unassigned ap joepeck nvasilyev oldest_to_newest 1061620 0 burg 2015-01-15 13:22:22 -0800 These wrong line numbers were previously visible in test results, but with the fix to https://bugs.webkit.org/show_bug.cgi?id=140478 this will become more apparent. This may have been happening for console messages too, though I have no test case in hand. I suggest simplifying the logic in ConsoleMessage and ScriptCallStackFactory so that there is only one place that creates a ScriptCallStack. Clients can specifically ask for the first non-native call frame if that is necessary, i.e., when the native call frame shouldn't be shown in the console. There's no reason to decide whether to skip this when creating the call stack, as code paths already exist to filter out native frames.