From:	Ian Chapman <ichapman AT nortelnetworks DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Overrun error in gdb
Date:	Fri, 24 Mar 2000 11:16:54 -0500
Organization:	Nortel
Lines:	21
Message-ID:	<38DB94F6.E225CA7B@nortelnetworks.com>
References:	<8b83ur$men$1 AT talia DOT mad DOT ttd DOT net>
NNTP-Posting-Host:	bcarib90.ca.nortel.com
Mime-Version:	1.0
X-Mailer:	Mozilla 4.7 [en] (Win95; U)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,
	I guess that gdb is slowing down your program.  If you set a trap to
watch for a bug writing to some location it will be really slow.  To do
what you seem to be doing you need an ICE (In Circuit Emulator).  The
last time I used an ICE was on a Mc68000 system.  I'm not able to
imagine an ICE running full speed on a Pent3 1G or whatever is coming
next.  The last time I looked into that Intel were making or considering
special processors with the internals accessible for traps.

		Regards Ian.

Francisco Pastor wrote:
> 
> I have made a program with djgpp that use serial port comunications with
> interrupt handlers. The program work fine but when I run it with gdb overrun
> errors appear. That occur even with relative slow speed (2400 bps) in a
> 100MHz 486 DX4.
> 
> My doubt is if gdb affect to DPMI interrupt management.
> 
> Thank's

- Raw text -