Replies: 5 comments
|
Hi, |
|
Hi, |
|
Hi Team, Could you please help take a look at this issue? If any part of the problem statement is unclear, please let me know. I'm happy to provide additional details, logs, or any other information that may help with the investigation. |
|
It's been fixed in 1.12.3. See #1404; not sure why Github didn't post an update here. |
|
Thanks for the update. Glad to hear the issue has been fixed. |
Uh oh!
There was an error while loading. Please reload this page.
Hi Team,

I am trying to use the CodeLLDB Memory View feature to dump and view memory in the webview.
When I attempt to read memory at the 64-bit address 0xffffff86bb21e0e0, I see error : " Internal debugger error : number too large to fit in target type"
While checking the issue, I noticed that in handle_read_memory() the memoryReference appears to be parsed as a signed 64-bit integer (i64). Since the address 0xffffff86bb21e0e0 exceeds the positive range of a signed 64-bit integer, the conversion seems to fail and results in the above error.

As memory addresses are typically treated as unsigned 64-bit values (u64), especially on 64-bit targets where valid addresses may reside in the upper address space, this appears to be the root cause of the issue.
Could you please take a look on this?
All reactions