Fixed regex so that start, end and offset are correctly parsed from maintenance command output #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The regex used for parsing the maintenance output fails if there are multiple colons(':') in the output line such as this line:
'[2] 0x0040026d->0x0040028e at 0x0000026d: .data: ALLOC LOAD READONLY DATA HAS_CONTENTS'
The output of current regex is
[('0x0040026d', '0x0040028e', '0x0000026d: .data', 'ALLOC', 'LOAD READONLY DATA HAS_CONTENTS')]
which results in offset(index 2) not being computed correctly and thus context registers displaying usage message. The correct output should be
[('0x0040026d', '0x0040028e', '0x0000026d' , '.data', 'ALLOC', 'LOAD READONLY DATA HAS_CONTENTS')]
The new regex in this pull request matches addresses and offset value more closely by looking for hexadecimal characters.