Date: Wed, 22 Mar 2000 11:25:22 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Francisco Pastor <fpastor DOT etra-id AT etra DOT es>
cc: djgpp AT delorie DOT com
Subject: Re: Overrun error in gdb
In-Reply-To: <8b83ur$men$1@talia.mad.ttd.net>
Message-ID: <Pine.SUN.3.91.1000322112450.17945n@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 21 Mar 2000, 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.

On what OS is this?  If it's DOS, please post here the contents of
your CONFIG.SYS and AUTOEXEC.BAT.

Also, what version of GDB is that?

> My doubt is if gdb affect to DPMI interrupt management.

Do the overruns happen even if you don't set any breakpoints in the
debugged program?  That is, do you see the overruns when you do
something like this:

	  gdb yourprog
	  r <put here any arguments needed by the program>

GDB (well, actually the DJGPP debug support functions linked into
GDB) hooks the timer and keyboard hardware interrupts, so it could
theoretically slow down programs which use those, but it does nothing
with the serial interrupt.  So, as long as you don't set any
breakpoints, there should be no slow-down due to GDB, I think.