From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii To: ezannoni@cygnus.com Cc: fnasser@cygnus.com, gdb-patches@sources.redhat.com, ac131313@cygnus.com Subject: Re: RFA: Remove unused synchronous code Date: Sat, 24 Mar 2001 12:34:00 -0000 Message-id: <200103242034.PAA20026@indy.delorie.com> References: <15031.47958.387059.980177@kwikemart.cygnus.com> <15032.49809.72980.803946@kwikemart.cygnus.com> X-SW-Source: 2001-03/msg00453.html > From: Elena Zannoni > Date: Wed, 21 Mar 2001 10:02:41 -0500 (EST) > > Eli Zaretskii writes: > > > > On Tue, 20 Mar 2001, Elena Zannoni wrote: > > > > > Eli has a point. > > > I would like to close this issue and leave things as they are > > > for the 5.1 release. > > > > FYI: I have a known bug with using the async code in the DJGPP port. > > If you type quickly, sometimes characters get stuck in some buffer, > > and GDB becomes out of sync with user keystrokes; i.e. you type a key, > > but GDB sees the previous key. > > Ah, thanks. I suspect there are a few (several?) bugs that still needs > to be ironed out. > > > I don't yet know whether this is due to some bug in the DJGPP's > > version of `select' or something in GDB's own code. It's the next > > issue I will be working on RSN, and I hope to get it solved for v5.1. > > > > Let me know if i can do something. > Have you seen this anywhere else other than DJGPP? I debugged this. It's a bug in DJGPP's library (`select' wasn't paying attention to characters buffered by the termios emulation). After fixing it, the -async option is working correctly in the DJGPP port.