call + pop pattern not handled by default

In shellcode, this pattern is used quite often. It uses a combination of call + pop to load the address of a string into a register.

Note, the default behavior is even more problematic -- the disassembly would continue to disassemble the string "VirtualProtect" and produce garbage. To get what is shown in the image, I have already set the function to a no-return to stop the control flow.

The tricky part of this is there is no easy way to handle this. If we wish to patch the code, the space is not enough. We would have to create a new segment and put some code there, which is complex

Reproduce the shellcode call+pop pattern described in the issue and compare the default disassembly with the manually configured no-return result. Investigate how the default control flow handles the string "VirtualProtect"; done means the pattern no longer causes the string to be disassembled as garbage without manual function configuration.