Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Crash in node.js #514

Closed
luyahan opened this issue Nov 8, 2021 · 3 comments
Closed

Crash in node.js #514

luyahan opened this issue Nov 8, 2021 · 3 comments

Comments

@luyahan
Copy link
Collaborator

luyahan commented Nov 8, 2021 

(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)
(node:141309) internal/test/binding: These APIs are for internal testing only. Do not use them.
(Use `node --trace-warnings ...` to show where the warning was created)


#
# Fatal error in ../deps/v8/src/codegen/riscv64/assembler-riscv64.cc, line 421
# Debug check failed: IsJalr(instr_I) || IsAddi(instr_I).
#
#
#
#FailureMessage Object: 0x3e79038320
Command: out/Debug/node /home/luyahan/node/test/wpt/test-webcrypto.js
--- CRASHED (Signal: 5) ---
@lazyparser
Copy link
Collaborator

Would you like to submit a build script to plctlab/riscv-ci?

targos pushed a commit to targos/abi-stable-v8 that referenced this issue Nov 9, 2021
@luyahan
[riscv64] Add block before LoadAddress
77599ff 
fix node.js DCHECK failed
issue: riscv-collab/v8#514

Change-Id: I07f40e6aca05be3eb7304a43235185fd40ebc1f2
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3260979
Reviewed-by: ji qiu <qiuji@iscas.ac.cn>
Commit-Queue: ji qiu <qiuji@iscas.ac.cn>
Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
Cr-Commit-Position: refs/heads/main@{#77750}
@luyahan
Copy link
Collaborator Author

luyahan commented Nov 15, 2021

Would you like to submit a build script to plctlab/riscv-ci?

i add it on plctlab/riscv-ci#38

@luyahan
Copy link
Collaborator Author

luyahan commented Nov 18, 2021

fixed

@luyahan luyahan closed this as completed Nov 18, 2021
luyahan added a commit to luyahan/nodejs-riscv64 that referenced this issue Jan 17, 2022
@luyahan
deps: V8: backport 77599ffe0a74
a4fb9ee 
Original commit message:

    [riscv64] Add block before LoadAddress

    fix node.js DCHECK failed
    issue: riscv-collab/v8#514

    Change-Id: I07f40e6aca05be3eb7304a43235185fd40ebc1f2
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3260979
    Reviewed-by: ji qiu <qiuji@iscas.ac.cn>
    Commit-Queue: ji qiu <qiuji@iscas.ac.cn>
    Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
    Cr-Commit-Position: refs/heads/main@{#77750}

Refs: v8/v8@77599ff
luyahan added a commit to luyahan/nodejs-riscv64 that referenced this issue Jan 17, 2022
@luyahan
deps: V8: backport 77599ffe0a74
f18bb63 
Original commit message:

    [riscv64] Add block before LoadAddress

    fix node.js DCHECK failed
    issue: riscv-collab/v8#514

    Change-Id: I07f40e6aca05be3eb7304a43235185fd40ebc1f2
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3260979
    Reviewed-by: ji qiu <qiuji@iscas.ac.cn>
    Commit-Queue: ji qiu <qiuji@iscas.ac.cn>
    Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
    Cr-Commit-Position: refs/heads/main@{#77750}

Refs: v8/v8@77599ffe0a74
danielleadams pushed a commit to nodejs/node that referenced this issue Jan 30, 2022
@luyahan @danielleadams
deps: V8: backport 77599ffe0a74
036650e 
Original commit message:

    [riscv64] Add block before LoadAddress

    fix node.js DCHECK failed
    issue: riscv-collab/v8#514

    Change-Id: I07f40e6aca05be3eb7304a43235185fd40ebc1f2
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3260979
    Reviewed-by: ji qiu <qiuji@iscas.ac.cn>
    Commit-Queue: ji qiu <qiuji@iscas.ac.cn>
    Auto-Submit: Yahan Lu <yahan@iscas.ac.cn>
    Cr-Commit-Position: refs/heads/main@{#77750}

Refs: v8/v8@77599ffe0a74

PR-URL: #41566
Refs: v8/v8@d8dc66f
Refs: v8/v8@3cab84c
Refs: v8/v8@471f862
Refs: v8/v8@77599ff
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lazyparser @luyahan