This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: Ctrl-C interrupt problem.
- To: "GDB (E-mail)" <gdb at sourceware dot cygnus dot com>
- Subject: RE: Ctrl-C interrupt problem.
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Tue, 14 Nov 2000 16:37:47 -0800
Hi,
I forward here a answer to my problem made by Fernando on the insight mail
list. I posted something on insight list because the problem appeared a
little different.
Following Fernando suggestion, I will continue discussion (it's more a
monologue for now but...) here trying to solve the 'pure' gdb problem first.
I've added my comments and answers to Fernando message...
> -----Original Message-----
> From: Fernando Nasser [mailto:fnasser@cygnus.com]
> Subject: Re: Ctrl-C interrupt
>
> Fabrice,
>
> I have no idea of what is going on. At the moment, I do not
> have the right setup to reproduce this situation (it may
> change in a couple of months, but I guess you
> would not want to wait that long).
Well no for sure,
So if anybody try to reproduce the problem with a similar configuration,
please let us know.
As a reminder, the problem appeared on a NT4+cygwin host connected via TCP
to a i386 target.
I don't think the target is involved. I think the bug is either in the way
cygwin handle ctrl-C and signal, or in the way gdb handle signal in the TCP
case.
I would like to test the case with a linux host, but i don't have any here
right now.
So if somebody try to reproduce the problem with a linux host, please let us
know the outcome.
It maybe a cygwin related problem, so if anybody has heard of a similar
problem with something else than gdb please let us know.
I also tried to debug my i386-elf-gdb with native cygwin insight but the
problem is that a Ctrl-C will be caught by the native debugger not the
debuggee.
I have absolutely no experience in debugging a debugger so if you have
tips,please let me know....
(Yes, there's a lot of thing that I need you to let me know)
Thanks
-- Fabrice Gautier
(And now then end of forwarded fernando message:)
> You stated debugging it right, so I guess you have a good
> chance to nail it.
> I suggest you leave the GUI debug to after you figure out
> what is going on
> in the command line mode. The text mode is an easier execution model.
>
> As you already know that the interrupt is not caught the
> second time around,
> all you have to figure now is right.
>
> At some point, the interrupt handler for Ctrl-C is installed.
> If I recall right
> (I have no time to look at this now), it is replaced when the
> inferior stops and
> has to be reinstalled again. I would bet that is not being
> reinstalled.
>
> Post your findings so we can help you with the next step, but
> do it at the
> gdb list as (on this first moment) the GUI is not involved.
>
> P.S.: When you say "target remote" you are using the
> non-async version,
> so don't worry about the async code in remote.c
>
> Fernando