Type 'page <addr>' in debugger and you will get the full mapping together with extra info.</addr>
You also have SF patch for debugger which improves 'info tab' but it is unefficient. The problem that could be to much pages in long mode so creating a list of them culd take a lot of time and memory.
Stanislav
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey, when one issues "info tab", he expects to see entire mapping, right? Speed of this command shouldn't be argument for not implementing it properly; sometimes you need to check all mappings, debugging own paging code - and you cannot, because... "info tab" is limited, because it would be "slow"? Most important factor when evaluating debugging features is usefulness, not speed...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What do you mean ?
Type 'page <addr>' in debugger and you will get the full mapping together with extra info.</addr>
You also have SF patch for debugger which improves 'info tab' but it is unefficient. The problem that could be to much pages in long mode so creating a list of them culd take a lot of time and memory.
Stanislav
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
Hey, when one issues "info tab", he expects to see entire mapping, right? Speed of this command shouldn't be argument for not implementing it properly; sometimes you need to check all mappings, debugging own paging code - and you cannot, because... "info tab" is limited, because it would be "slow"? Most important factor when evaluating debugging features is usefulness, not speed...
View and moderate all "feature-requests Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Feature Requests"
And, hmm, I didn't notice that patch before, I will give it a shot...
Already resolved