Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(93)

Issue 555170: Show user script source line that caused exception intead of a line in a nati... (Closed)

Created:
10 years, 10 months ago by yurys
Modified:
9 years, 7 months ago
CC:
v8-dev
Visibility:
Public.

Description

Show user script source line that caused exception intead of a line in a native script. When an error is reported as one happened in a native script it's hard to track the original cause. See chromium issue: http://crbug.com/25305 Committed: http://code.google.com/p/v8/source/detail?r=3753

Patch Set 1 #

Patch Set 2 : '' #

Unified diffs Side-by-side diffs Delta from patch set Stats (+44 lines, -2 lines) Patch
M src/frames.h View 1 chunk +3 lines, -0 lines 0 comments Download
M src/frames.cc View 1 2 chunks +10 lines, -2 lines 0 comments Download
M test/cctest/test-api.cc View 1 chunk +31 lines, -0 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
yurys
10 years, 10 months ago (2010-01-29 18:51:55 UTC) #1
Søren Thygesen Gjesse
LGTM Consider adding a test to tets/mjsunit/stack-traces.js as well.
10 years, 10 months ago (2010-02-01 09:21:20 UTC) #2
yurys
Runtime_CollectStackTrace doesn't use StackTraceFrameIterator and is not affected by this change. I'm not sure if ...
10 years, 10 months ago (2010-02-01 10:27:40 UTC) #3
yurys
10 years, 10 months ago (2010-02-01 10:28:52 UTC) #4
I could prepare another change that changes exception stack trace behavior if we
agree that it's the right approach.

On 2010/02/01 10:27:40, Yury Semikhatsky wrote:
> Runtime_CollectStackTrace doesn't use StackTraceFrameIterator and is not
> affected by this change. I'm not sure if we want to exclude all the frames
with
> functions from native scripts. If we want to do so, we could probably use
> StackTraceFrameIterator instead of StackFrameIterator in
> Runtime_CollectStackTrace. Probably it's not that bad to show builtin
functions
> in the stack trace since in the case of stack trace user is still able to
track
> the source of error  (unlike error message handler where the stack may not be
> available).
> 
> On 2010/02/01 09:21:20, Søren Gjesse wrote:
> > LGTM
> > 
> > Consider adding a test to tets/mjsunit/stack-traces.js as well.

Powered by Google App Engine
This is Rietveld 408576698