delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/03/22/13:24:18

Date: Wed, 22 Mar 2000 22:31:45 +0500
Message-Id: <200003221731.WAA01014@midpec.com>
From: tr AT midpec DOT com (Prashant TR)
To: djgpp AT delorie DOT com
In-reply-to: <8b83ur$men$1@talia.mad.ttd.net> (fpastor.etra-id@etra.es)
Subject: Re: Overrun error in gdb
References: <8b83ur$men$1 AT talia DOT mad DOT ttd DOT net>
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

"Francisco Pastor" <fpastor DOT etra-id AT etra DOT es> proclaimed:

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

Seems quite obvious. You shouldn't be stepping through something that handles
serial ports. If you try to do that, data gets flooded onto the serial port
causing an overrun. But if you're getting a problem by just _running_ (not
stepping) the program under GDB, that would be another issue, I guess.

What you could probably do is to run all hardware specific code at one go (use
a breakpoint to do this).

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019