The regex'es for the GHS parser match Global Symbols which they should not.
## Observed behaviour
It should not match for example:
00000000+000000 D GetWriteBlock..libs.some.global..symbol.blah.blub.
but currently it does.
I figured this out since the address translation failed warning appeared. From the FQN it seems that only the section regex might be affected.
Possibly we can stop if a line starts with Global Symbols minus leading spaces. However we should check if we always can rely on this order: Sections Summary -> Object Summary -> Global Symbols
Description
The regex'es for the GHS parser match Global Symbols which they should not. ## Observed behaviourIt should not match for example:
but currently it does.
I figured this out since the address translation failed warning appeared. From the FQN it seems that only the section regex might be affected.
Possibly we can stop if a line starts with
Global Symbolsminus leading spaces. However we should check if we always can rely on this order: Sections Summary -> Object Summary -> Global Symbols