Skip to content

Conversation

@oyyd
Copy link
Contributor

@oyyd oyyd commented Jul 8, 2019

When inspect or findrefs an invalid expr, llnode will print
an error message prefixed with "error: error: error:". This PR
will reduce one redundant "error:" for such scenario and it
seems that we can't remove the other redundant "error:" by
calling SB API only.

Before this PR:

(llnode) v8 inspect invalid_addr
error: error: error: use of undeclared identifier 'invalid_addr'
(llnode) v8 findrefs -v invalid_addr
error: error: error: use of undeclared identifier 'invalid_addr'

After:

(llnode) v8 inspect invalid_addr
error: error: use of undeclared identifier 'invalid_addr'
(llnode) v8 findrefs -v invalid_addr
error: error: use of undeclared identifier 'invalid_addr'

The other redundant "error:" seems to come from here and I couldn't find a way to remove it by calling SB API only.

@codecov-io
Copy link

codecov-io commented Jul 8, 2019

Codecov Report

Merging #285 into master will increase coverage by 0.23%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##           master    #285      +/-   ##
=========================================
+ Coverage   80.56%   80.8%   +0.23%     
=========================================
  Files          33      33              
  Lines        4116    4120       +4     
=========================================
+ Hits         3316    3329      +13     
+ Misses        800     791       -9
Impacted Files Coverage Δ
src/llnode.cc 75% <100%> (+1.87%) ⬆️
src/llscan.cc 61.31% <100%> (+0.58%) ⬆️
test/plugin/scan-test.js 98.97% <100%> (+0.06%) ⬆️
src/llv8.cc 76.11% <0%> (-0.16%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 640799a...b678289. Read the comment docs.

@oyyd oyyd force-pushed the format-error-message branch from bf744bf to 27d8016 Compare July 8, 2019 08:04
When `inspect` or `findrefs` an invalid expr, llnode will print
an error message prefixed with "error: error: error:". This PR
will reduce one redundant "error:" for such scenario and it
seems that we can't remove the other redundant "error:" by
calling SB API only.
@oyyd oyyd force-pushed the format-error-message branch from 27d8016 to b678289 Compare July 8, 2019 09:27
mmarchini pushed a commit that referenced this pull request Jul 19, 2019
When `inspect` or `findrefs` an invalid expr, llnode will print
an error message prefixed with "error: error: error:". This PR
will reduce one redundant "error:" for such scenario and it
seems that we can't remove the other redundant "error:" by
calling SB API only.

PR-URL: #285
Reviewed-By: Matheus Marchini <mat@mmarchini.me>
@mmarchini
Copy link
Contributor

Landed in 74414fc

@mmarchini mmarchini closed this Jul 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants