armhf segmentation fault --inspect-brk and simple import statement
Open
Nobody has claimed this yet.
confirmed-bug
inspector
v8 engine
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Version
18.13.0, 18.17.0
Platform
6.1.0-10-armmp #1 SMP Debian 6.1.38-1 (2023-07-14) armv7l GNU/Linux
Subsystem
inspector
What steps will reproduce the bug?
Execute
node --inspect-brk main.js
with these files:
import './odd.js';
and
class A extends URL {
constructor(str) {
super(str);
}
toString() {
return super.toString();
}
}
console.log("fail")
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
Not fail
What do you see instead?
Segmentation fault
Additional information
Reproduced with the debian package AND the latest nodesource package node 18.x on debian bookworm.
Small changes to odd.js will stop crashing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash with node --inspect-brk main.js on the reported armv7l Debian environment, using the main.js and odd.js examples in the issue. Trace the inspector startup path and confirm that the import no longer causes a segmentation fault under the same conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux, node.js
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100