× 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.


  • Subject: Re: Save breakpoints in Source Debug
  • From: Tim Truax <truax@xxxxxxxxx>
  • Date: Sat, 09 Jan 1999 09:44:07 -0500

Hello Ravi,
This is ISDB functionality that I also find useful.  See below:

1.  Exit your interactive source debugger session as usual.
    All commands you typed on the command line, and all other actions that
    affected the execution of the program, are stored in the file QIXALOG.
    (Commands that were run from a file with the USE command are also
    logged, although the USE command itself is commented out.)

2.  Since the log file may contain commands that are not valid, you may
    want to edit it before using it again so that you have a clean set of
    instructions.

3.  Copy the QTEMP/QIXALOG file to a file with a different name.  (This
    file is cleared the next time you use the STRISDB command, so you must
    copy it.)

4.  Enter the STRISDB command to start another debugging session for the
    same program.

5.  On the Source display command line, type USE followed by the name of
    the source physical file you copied QIXALOG to.


   USE QTEMP TEMP QIXALOG

Ravi wrote:

> IS it possible to save the breakpoints set up in ISDB and then invoke
> the same break points in a later session? ISDB creates files QIXALOG,
> QIXAMPF in QTEMP. When breakpoints are added they must be stored in one
> of these files. During the debug session, I don't find any entries in
> these files, and maybe when the program ends the files are cleared out.
> Any ideas??
>
> Thanks
>
>

___________________________________________________
«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Tok2YaLatR!
Tim & Dana Truax and ... Caleb 5 yrs!
___________________________________________________
«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»¥«¤»§«¤»
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.