-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
lldb jlh command has stopped working #29667
Comments
I think I've ran into this in the v8 upstream and I had to take some |
V8 doesn't use heap classes as pointers to the heap anymore. Instead, those classes are concrete C++ objects with a ptr_ field. This was part of a larger initiative to make V8 UBSAN-compliant, the commits which lead to this change can be seen in the tracking issue: https://bugs.chromium.org/p/v8/issues/detail?id=3770&q=3770&can=2. Design document to move from object pointers to concrete objects can be found here: https://docs.google.com/document/d/1_w49sakC1XM1OptjTurBDqO86NE16FH8LwbeUAtrbCo/edit#heading=h.8wg7tpqbpt7m I'll close this as answered, but feel free to reopen if you want. |
I've opened a pull request for the lldb |
In the meantime, the gdb shortcuts work great. |
The lldb command
jlh
has stopped working for me. At the moment this is what happens if I run it:(lldb) jlh arg
(The output is just a blank line). The expected output in this case would be:
Looking at lldb_commands.py this cast seems to be the issue, at least for the
jlh
command and removing it fixes the issue for me.I know that we don't maintain lldb_commands.py but I wanted to ask if anyone else has run into this before looking into it closer and perhaps opening an issue upstream.
The text was updated successfully, but these errors were encountered: