home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!usenet.coe.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu!news
- From: holland@matt.ksu.ksu.edu (Rich Holland)
- Newsgroups: comp.lang.pascal
- Subject: New Idea!
- Message-ID: <188jleINNcn6@matt.ksu.ksu.edu>
- Date: 4 Sep 92 11:15:26 GMT
- Article-I.D.: matt.188jleINNcn6
- Organization: Kansas State University
- Lines: 29
- NNTP-Posting-Host: matt.ksu.ksu.edu
-
- I've got a rather large program which is spread out through around 10
- units, and over 6500 lines of code. When it crashes mysteriously, I
- get a message like this:
-
- Runtime error 105 at 0052:03A3
-
- I can then look at 'PROG.MAP' (the map file I told it to generate) and
- search for '0052:03A3' and get a line number. Then, I have to page
- back through the map file a few pages, usually, and find the Unit name
- the line number is in. Then, I go into Qedit and PgDn until I get to
- that line number.
-
- Question 1: Is there a way to jump to a given line in Qedit? Like a
- macro you could use (Alt-J for Jump?) and enter the line number to go
- to?
-
- Question 2: Anyone (other than me) be interested in (or know of!) a
- program to grab the runtime error off the screen (from video memory),
- load up an editor with the file (Qedit, or an internal editor), and
- jump to the offending line??
-
- I think (2) has some possibilities! What about the rest of you?
- Anyone ever seen anything like this before??
-
- --
- Rich Holland | INTERNET: holland@matt.ksu.ksu.edu
- 100 Jardine Terr, Apt A7 | BITNET : holland@ksuvm
- Manhattan, KS 66502-3357 | UUCP : ...!rutgers!matt.ksu.ksu.edu!holland
- char*p="char*p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
-