Re: Break point -- MI400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

From: Steve Richter

To: MI400@midrange.com

Sent: Monday, June 04, 2001 4:37 PM

Subject: Re: Break point

From: Steve Richter

A debugger feature plea: When in debug mode, provide an "AddAddrBkp" cmd. When an address range is referenced in the job being debugged, call a debug handler pgm. Similar to the action of the breakpoint handing pgm that is called when an instruction is executed.

===> that may be hard. The way the orignal breakpoint (BRK "here") is by compiling into a dummy instruction.

Is you ADDBKP "here", the dummy instruction is actually replaced in the program object by a trap instruction.

Leif,

When you AddBkp, a trap instruction is inserted in the pgm object?

===> yes, absolutely

What happens when the pgm is called by a non debug mode job?

===> the trap that is taken detects that the program is not under debug

in this job and does nothing. I didn't design this :-)

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.