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.

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

Yarn segfaults on latest commit #48590

Closed
theoparis opened this issue Jun 29, 2023 · 2 comments
Closed

Yarn segfaults on latest commit #48590

theoparis opened this issue Jun 29, 2023 · 2 comments

Comments

@theoparis
Copy link

Version

v21.0.0-pre

Platform

Linux gigamachine 6.4.0-0.rc7.20230623git8a28a0b6f1a1.57.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jun 23 17:51:48 UTC 2023 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

  • Build node from source, with the latest bleeding edge commit from github
  • Attempt to use yarn@canary to add any package from npm

How often does it reproduce? Is there a required condition?

Yarn works fine until you try to add a new package.

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

➜ yarn add simple-git
➤ YN0000: ┌ Resolution step
➤ YN0000: └ Completed in 1s 762ms
➤ YN0000: ┌ Fetch step
Segmentation fault: oops, process 'yarn' core dumped
Error: nu::shell::external_command

× External command failed
╭─[entry #186:1:1]
1 │ yarn add simple-git
· ──┬─
· ╰── core dumped
╰────
help: Segmentation fault: child process 'yarn' core dumped

Additional information

yarn set version canary
yarn add xyz

I am running fedora rawhide by the way. If I need to i can enable debug builds of node.js to further debug the segmentation fault. However I'm not sure how to use lldb with yarn.

@bnoordhuis
Copy link
Member

You should be able to get a stack trace from the core file, it's the -c switch to lldb. You can turn on core dumps with ulimit -c unlimited and if you don't see it in the working directory, check sysctl kern.corefile.

I may ask you to try again with a debug build but usually the stack trace from a release build is good enough.

@avivkeller avivkeller closed this as not planned Won't fix, can't repro, duplicate, stale Aug 10, 2024
@avivkeller
Copy link
Member

Hey, it's been over a year since any activity on this issue. Given that this was an issue with a bleeding edge past version, I assume it's been resolved. If that's not the case, and this is an issue in the latest version, please open an issue against yarn, or in nodejs/help.

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

No branches or pull requests

3 participants