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
--gdbjit segfaults in semver #7785
Comments
@BenLubar would you be able to test this on some earlier versions of 4.x and see if this is a regression or a problem that has always existed? Maybe try v4.2.0 to start as it was the first LTS. |
@BenLubar Can you post the output of |
@thealphanerd I tried it on 6.3.0 earlier and the same crash happened. I'll compile 4.2.0 now and try that. |
@thealphanerd 4.2.0 does not crash. |
4.3.0 also does not crash. |
The crash appeared somewhere between 4.4.2 and 4.4.3 |
I'm guessing it is aadf356aa2 /cc @bnoordhuis |
@BenLubar can you do a run with that commit reverted? |
/cc @nodejs/v8 @ofrobots (sorry for the spam) |
@BenLubar what are you using |
@ofrobots we are trying to debug something that's causing our forum software to hang, so I made this script: https://github.com/boomzillawtf/tdwtf/blob/04633e03478ceffe5779706c40e408312b48c729/watchdog.bash However, it only has symbols for the threads that are waiting on locks and semaphores, not the thread that's running the forum code. We haven't had this running successfully yet on any version of NodeJS. |
@thealphanerd it compiles and runs, but the symbols are not generated. |
Okay, if you're interested in JS stack traces you might also want to look into the The crash you reported needs investigation, but hopefully the gdbinit trick works for you for now. Very few people are using |
https://gist.github.com/BenLubar/e39e13628496661eb5818a0a0bf2f43e
|
Does anyone know if this is still an issue or if it got fixed? |
Unfixed, most likely. gdb-jit.cc has seen no real changes upstream since this issue was raised. |
Closing due to lack of activity. Let me know if we should re open |
--gdb
--gdbjit
is activeNodeJS segfaults when --gdbjit is active. The crash looks like memory corruption:
https://gist.github.com/BenLubar/93c545491a4db3d1d6bdd75090474da3#file-gistfile1-txt
I've narrowed the code that causes the crash down to this reproduceable test case:
https://gist.github.com/BenLubar/064b65170ae1f01ea00328b537eaefba
The text was updated successfully, but these errors were encountered: