-
Notifications
You must be signed in to change notification settings - Fork 100
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
bug(print-source): libc++abi: terminating with uncaught exception #422
Comments
tony-go
changed the title
bug(inspect -s): libc++abi: terminating with uncaught exception
bug(print-source): libc++abi: terminating with uncaught exception
Sep 28, 2022
kvakil
added a commit
to kvakil/llnode
that referenced
this issue
Oct 1, 2022
This "fixes" the segfault reported in nodejs#422, in the sense that you no longer get a segfault. However the printing does not actually work, i.e. you currently get an error like this: ```console (lldb) v8 i -s 0x2196b1a09a29 error: Invalid source range, start_pos=3108, len=-3098, source_len=10 ``` I'm deeming this better than segfaulting. We should really never be segfaulting as the coredump might be incomplete/partially corrupted. (Also, we already know function printing on v16 doesn't work right now.)
kvakil
added a commit
to kvakil/llnode
that referenced
this issue
Oct 1, 2022
This "fixes" the crash reported in nodejs#422, in the sense that you no longer get a crash. However the printing does not actually work, i.e. you currently get an error like this: ```console (lldb) v8 i -s 0x2196b1a09a29 error: Invalid source range, start_pos=3108, len=-3098, source_len=10 ``` I'm deeming this better than crashing. We should really never be crashing as the coredump might be incomplete/partially corrupted. (Also, we already know function printing on v16 doesn't work right now.)
No9
pushed a commit
that referenced
this issue
Oct 18, 2022
This "fixes" the crash reported in #422, in the sense that you no longer get a crash. However the printing does not actually work, i.e. you currently get an error like this: ```console (lldb) v8 i -s 0x2196b1a09a29 error: Invalid source range, start_pos=3108, len=-3098, source_len=10 ``` I'm deeming this better than crashing. We should really never be crashing as the coredump might be incomplete/partially corrupted. (Also, we already know function printing on v16 doesn't work right now.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
llnode crashes when I run
v8 i -s <addr>
.To reproduce
crash.js
node --abort-on-uncaught-exception crash.js
v8 bt
:v8 i -s 0x2f03a7693201
:Expected behavior
Having the source of the function printed in the console.
Console output
Local environment (please complete the following information):
4.0.0
lldb-1400.0.30.3
16.17.0
Server where the core was dumped (please complete the following information):
Same as above.
Additional context
The text was updated successfully, but these errors were encountered: