Well... in a sense, that depends upon the debugging tool that you are
using... Because different tools have different mechanisms. So, what
tool are you using.
On the other hand, one thing I can say unequivocally: When you set
breakpoints of any sort into common storage modules, and you don't
know what you are doing, the results have a high probability of being
bad. The consequences can range from failed address spaces to whole
System crashes!
Generally, any breakpoint that is set into common storage is visible
to all address spaces and can potentially be executed by any address
space. For most tools, absent the existence of a debugging
environment in the victim aspace, the result will be a failure of one
sort or another.
If you want anything more specific, you will need to indicate what
debugging tool you are using and what module you are considering
breakpointing, and what your actual objective is.
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: [email protected]
Home page: www.xdc.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
At 9/12/2014 12:53 PM, Jake anderson wrote:
Hi
Apology for being ignorant or just a silly question.
Whats the impact of setting breakpoint on any module which are currently
being used by the systems ? For example setting Breakpoint on IEFBR14.
Jake
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: <mailto:[email protected]>[email protected]
Home page: www.colesoft.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
