Skip to content
This repository has been archived by the owner on Nov 19, 2024. It is now read-only.

Show variables in memory view #26

Closed
wants to merge 2 commits into from

Conversation

paul-marechal
Copy link
Member

Rebased version of #22 by @simark

@paul-marechal paul-marechal force-pushed the simark/variables-in-memory-view branch 2 times, most recently from 53288a7 to dbcf20a Compare April 10, 2019 23:22
@paul-marechal
Copy link
Member Author

Apparently there is a bug where we cannot scroll anymore.

@vince-fugnitto vince-fugnitto force-pushed the simark/variables-in-memory-view branch from dbcf20a to efd9b6a Compare July 30, 2019 17:31
In theory, we could have problems reading addresses as JS numbers, since
JS numbers don't have full 64 bits precision.  This patch makes use of
the 'long' library, which stores 64-bit numbers as two 32-bit halves.

Signed-off-by: Simon Marchi <[email protected]>
Signed-off-by: Paul Maréchal <[email protected]>
This patch makes it so we hightlight the local variables of the current
frame in the memory view.  The idea is simple, we get the size and
address of all locals of the current frame through GDB (sizeof(foo) and
&foo).  If the bytes backing these variables are in the scope of the
memory view, we highlight them with a different color for each variable.

Signed-off-by: Simon Marchi <[email protected]>
Signed-off-by: Paul Maréchal <[email protected]>
Signed-off-by: Vincent Fugnitto <[email protected]>
@vince-fugnitto vince-fugnitto force-pushed the simark/variables-in-memory-view branch from efd9b6a to 93bee9a Compare July 30, 2019 17:32
@vince-fugnitto
Copy link
Member

I've rebased the PR on the latest changes, and fixed the issue regarding the scrolling.

@marechal-p can you confirm that scrolling works correctly as before?

@colin-grant-work
Copy link
Contributor

@marechal-p, @vince-fugnitto, This is a feature our users have been requesting. Is it still planned to merge this PR?

@vince-fugnitto
Copy link
Member

@marechal-p, @vince-fugnitto, This is a feature our users have been requesting. Is it still planned to merge this PR?

I believe so, it was forgotten for a while now so I'll rebase it and re-test.
Please let me know if you're interested in testing/contributing to the pull-request.

@vince-fugnitto
Copy link
Member

Closing in favor of #111.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants