RE: Ctrl-C interrupt problem.

[Fabrice Gautier <Fabrice_Gautier@sdesigns.com>]

Well, 

I don't know how, but half the problem is resolved by upgrading to CVS
version.

"half" means that i can't crash gdb with ctrl-C anymore with a native
target.

However the frist half (second ctrl-C is not caught by a remote i386-elf
target) is still there.

Thanks

-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com 
From Fabrice_Gautier@sdesigns.com Wed Nov 15 20:46:00 2000
From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: gdb@sources.redhat.com
Cc: "Ecos-List (E-mail)" <ecos-discuss@sourceware.cygnus.com>
Subject: RE: Ctrl-C interrupt problem.
Date: Wed, 15 Nov 2000 20:46:00 -0000
Message-id: <B1F6452C89AFD411AE0800A0CC734C23015020@EMAIL1>
X-SW-Source: 2000-11/msg00181.html
Content-length: 800

[eCos and RedBoot guys, I think this may concern you 
 its about a ctrl-C problem which only happen when debugging via ethernet.
 full story in the gdb list archives ]

I Got it! 
Well, i hope....

And it make sens why it only happens with TCP...

The problem is that when gdb send the continue packet to the target, it wait
for the target to send the '+' Ack. During this time the SIGINT handler is
not set.

My guess is that RedBoot intedn to send it BUT (tata) the ethernet driver
just wait to have a full packet before really sending! So this happen when a
O packet is sent.

So i guess the only thing needed in RedBoot is to add a "flush" somewhere.
I'm not sure at what level, but i'll look at it tomorrow if nobody does it
before.

Thanks

-- 
Fabrice Gautier
fabrice_gautier@sdesigns.com