Xref: news-dnh.mv.net comp.os.msdos.djgpp:3797
Path: news-dnh.mv.net!mv!news.sprintlink.net!hk.gin.net!news.hk.net!hpg30a.csc.cuhk.hk!agate!news.ucdavis.edu!library.ucla.edu!newsfeed.internetmci.com!usenet.eel.ufl.edu!news.ultranet.com!bigboote.WPI.EDU!news3.near.net!ray.com!news.ray.com!news.res.ray.com!swlnews.msd.ray.com!usenet
From: Robert=Hazard AT msd DOT ray DOT com (Bob Hazard)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Debugging
Date: 12 Dec 1995 12:47:01 GMT
Organization: Raytheon Company
Lines: 24
References: <DJFCBI DOT Dnt AT jade DOT mv DOT net>
Nntp-Posting-Host: ircpc-0178.msd.ray.com
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

In article <DJFCBI DOT Dnt AT jade DOT mv DOT net>, eliz AT is DOT elta DOT co DOT il says...
>
>GDB should work, both in DPMI and non-DPMI mode.  Can it be that your 
>memory options in the PIF file for DOS box are set too low?
>
>Does it work outside Windows (with gdb, not gdb-dpmi, of course)?

 Yes, it does work outside of Windows.  That is, the non-dpmi version allows
me to set breakpoints and step past them without error signals.  I am not
sure how mem would cause an illegal instruction signal, but anything's
possible.  I have had the same performance on two different installations
(differing machines) now.  MSDOS (non-dpmi works), and Windows/DOS shell
(dpmi version of gdb) doesn't.  I assume that you have been able to use gdb
under Windows ???   I am hoping that it is just something simple I am doing
wrong.  My editor of choice is a Windows program.... 


-- 
Robert Hazard          work: Robert=Hazard AT msd DOT ray DOT com
                      other: BobHazard AT aol DOT com, Bobh AT channel1 DOT com or
                             Rhazard AT nyx DOT cs DOT du DOT edu
* Opinions expressed herein are exclusively my own and do not 
* necessarily represent the thoughts or opinions of my employer.