public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* GDB, m68k-coff, remote debugging
@ 1999-03-25 11:42 sbhagava
  1999-03-31 19:45 ` sbhagava
  0 siblings, 1 reply; 2+ messages in thread
From: sbhagava @ 1999-03-25 11:42 UTC (permalink / raw)
  To: cygwin

     I'm trying to use GDB from NT and do remote debugging for m68k over 
     the serial line. 
     
        I have had problems with B19 to interrupt (Control-C) after a 
     "continue" command on the GDB. It looks like GDB doesn't get the 
     signal while it is waiting on the serial read(blocked).
     
     I upgraded my Cygwin to B20.1 tried compiling GDB and using it with 
     B20.1
     
     It helped to some extent and GDB is able to catch the signal 
     SIGINT while the serial read is blocked and while GDB is waiting for 
     something to come on the serial line. But, this works only one time. 
     GDB cannot get this signal anymore in the same shell session. Starting 
     a new GDB session in a new shell helps.
     
        Also, I downloaded the Jan 15th Snapshot and installed the 
     Cygwin-inst*. The problem with this version is that the GDB doesn't 
     get the signal at all while waiting for the serial read. It behaves 
     the same as Cygwin B19 behaved.
     
     I think the problem is in the handling of signals while doing the 
     blocked I/O calls.
     
     Any help or suggestions will be appreciated.
     
     Thanks,
     
     Satish Bhagavatula.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

^ permalink raw reply	[flat|nested] 2+ messages in thread
* GDB, m68k-coff, remote debugging
  1999-03-25 11:42 GDB, m68k-coff, remote debugging sbhagava
@ 1999-03-31 19:45 ` sbhagava
  0 siblings, 0 replies; 2+ messages in thread
From: sbhagava @ 1999-03-31 19:45 UTC (permalink / raw)
  To: cygwin

     I'm trying to use GDB from NT and do remote debugging for m68k over 
     the serial line. 
     
        I have had problems with B19 to interrupt (Control-C) after a 
     "continue" command on the GDB. It looks like GDB doesn't get the 
     signal while it is waiting on the serial read(blocked).
     
     I upgraded my Cygwin to B20.1 tried compiling GDB and using it with 
     B20.1
     
     It helped to some extent and GDB is able to catch the signal 
     SIGINT while the serial read is blocked and while GDB is waiting for 
     something to come on the serial line. But, this works only one time. 
     GDB cannot get this signal anymore in the same shell session. Starting 
     a new GDB session in a new shell helps.
     
        Also, I downloaded the Jan 15th Snapshot and installed the 
     Cygwin-inst*. The problem with this version is that the GDB doesn't 
     get the signal at all while waiting for the serial read. It behaves 
     the same as Cygwin B19 behaved.
     
     I think the problem is in the handling of signals while doing the 
     blocked I/O calls.
     
     Any help or suggestions will be appreciated.
     
     Thanks,
     
     Satish Bhagavatula.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


^ permalink raw reply	[flat|nested] 2+ messages in thread
end of thread, other threads:[~1999-03-31 19:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-03-25 11:42 GDB, m68k-coff, remote debugging sbhagava
1999-03-31 19:45 ` sbhagava

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).