-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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.
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
fs.fstat
results in an abort with some arguments
#55983
Labels
confirmed-bug
Issues with confirmed bugs.
fs
Issues and PRs related to the fs subsystem / file system.
Comments
jazelly
added
fs
Issues and PRs related to the fs subsystem / file system.
confirmed-bug
Issues with confirmed bugs.
labels
Nov 26, 2024
IIUC, a minimum reproducible example is like this.
I think we should validate |
jazelly
changed the title
Nov 26, 2024
lzma-native.parseFileIndexFD
results in an abort with some argumentsfs.fstat
results in an abort with some arguments
github-actions bot
pushed a commit
to aduh95/node
that referenced
this issue
Dec 4, 2024
PR-URL: nodejs#56000 Fixes: nodejs#55983 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jason Zhang <xzha4350@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
aduh95
pushed a commit
to aduh95/node
that referenced
this issue
Dec 4, 2024
PR-URL: nodejs#56000 Fixes: nodejs#55983 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jason Zhang <xzha4350@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
aduh95
pushed a commit
to aduh95/node
that referenced
this issue
Dec 4, 2024
PR-URL: nodejs#56000 Fixes: nodejs#55983 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jason Zhang <xzha4350@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
aduh95
pushed a commit
to aduh95/node
that referenced
this issue
Dec 4, 2024
PR-URL: nodejs#56000 Fixes: nodejs#55983 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jason Zhang <xzha4350@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
aduh95
pushed a commit
to aduh95/node
that referenced
this issue
Dec 4, 2024
PR-URL: nodejs#56000 Fixes: nodejs#55983 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Jason Zhang <xzha4350@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
confirmed-bug
Issues with confirmed bugs.
fs
Issues and PRs related to the fs subsystem / file system.
Version
v22.11.0
Platform
Subsystem
fs.fstat, v8
What steps will reproduce the bug?
the final package.json is as follows:
Then the node instance occurs an abort.
How often does it reproduce? Is there a required condition?
This abort can always be triggered following the steps above.
What is the expected behavior? Why is that the expected behavior?
If any error occurs, an exception or other similar error-reporting stuff should be thrown. There is no reason to abort the whole node process.
What do you see instead?
» node
Welcome to Node.js v22.11.0.
Type ".help" for more information.
1: 0xe19ca5 node::OnFatalError(char const*, char const*) [node]
2: 0x123f996 v8::Utils::ReportApiFailure(char const*, char const*) [node]
3: 0x10e8085 node::DetermineSpecificErrorType[abi:cxx11](node::Environment*, v8::Localv8::Value) [node]
4: 0xe38f71 [node]
5: 0xf8d068 [node]
6: 0x7d22ff20f5e2
----- JavaScript stack trace -----
1: fstat (node:fs:1531:11)
2: exports.parseFileIndexFD (/home/u24vm/Projects/nodejsfuzz/packages/package-cf2b3d61d5de70b987170d0fe1c84397/node_modules/lzma-native/index.js:526:13)
3: REPL4:3:22
[1] 742850 IOT instruction (core dumped) node
Additional information
No response
The text was updated successfully, but these errors were encountered: