X-Spam-Check-By: sourceware.org
From: "Charli Li" <KBarticle889459 AT aim DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: GDB Ctrl-C Interrupt Fails WORKAROUND
Date: Thu, 15 Jun 2006 17:28:59 -0400
Message-ID: <LLEBLEDLPAKFHFKGNDBMCEIJCBAA.KBarticle889459@aim.com>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <20060615192841.GA17101@trixie.casa.cgf.cx>
X-AOL-IP: 70.20.155.229
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
> Of Christopher Faylor
> Sent: Thursday, June 15, 2006 3:29 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: GDB Ctrl-C Interrupt Fails WORKAROUND
>
>
> On Thu, Jun 15, 2006 at 12:17:09PM -0700, Kyle McKay wrote:
> >On 15 Jun 2006 13:57:14 -0400, Christopher Faylor wrote:
> >>On Cygwin, gdb is the debugger for programs produced by gcc.  You are
> >>not going to be able to read many (any?) symbols for programs produced
> >>by other compilers so there really isn't much of a reason to use gdb
> >>to debug non-gcc-produced programs.
> >
> >Apparently you did not see my previous comments about this:
>
> No.  I didn't.  Same observation applies, though.
>
> >>On 15 Jun 2006 10:38:57 -0700, Kyle McKay wrote:
> >>>Now if you have such a program compiled with the m$ compiler for
> >>>which you do not have the source and such a program is loading a
> >>>DLL plugin built with cygwin that you're trying to debug then CTRL-
> >>>C WILL NEVER WORK no matter how many console windows you get out.
> >
> >DLLs built with gcc cannot be interrupted with CTRL-C when they are
> >loaded by programs built with other compilers.
> >
> >>In any event, at least we're getting details now beyond the "CTRL-C
> >>doesn't work with gdb".
> >
> >Or these comments about using a console window:
> >
> >>On 15 Jun 2006 10:38:57 -0700, Kyle McKay wrote:
> >>>It is also a non-solution for ssh users and remote X users.
>
> I mentioned ptys and ttys in my very first response.
>
> >CTRL-C also appears to be used by the X windows ddd break button.
> >Doesn't work there either.
>
> So, submit a ddd bug report.
>
> >However, in all these cases the debugbreak (debugbreak.c) utility can
> >provide a usable, if awkward, workaround.
>
> The keyword being "awkward".  There is nothing to stop an
> interested person
> from modifying gdb to do the right thing.
>
>
> >For example, build the loopdll.dll and runloop.exe from the following
> >sources using the gcc and m$ compilers as indicated:
>
> Isn't the m'$' compiler you're using actually free?  If so, the dollar
> sign appears to be misplaced.

Visual C++ 2005 Express Edition is free; all other editions are not.  The
only thing us Cygwin users use from MSVC++8 is cl.

>
> In any event, we seem to be looping:
>
> On Thu, Jun 15, 2006 at 01:57:14PM -0400, Christopher Faylor wrote:
> >It is also possible that CTRL-C will not interrupt programs which are
> >compiled for -mwin32.  I haven't tried that for a while.  That may
> >be what you're seeing when you use the Microsoft Visual C compiler.
>
> >/* BEGIN loopdll.c */
> >/* Compile with cygwin gcc -o loopdll.dll -g -mno-cygwin
> -mthreads - mdll loopdll.c */
> >/* Compile with m$ cl -o runloop.exe runloop.c */
>
> You sure love that 'm$' don't you?

Kyle probably wanted to imiatate the unix-like shells.  In some howtos, they
put in something like:

bash$

Or, as in "A Day With CVS", they put in:

floss$

So Kyle put in m$ to signify that he was using the vcvars32.bat file (or
something like that)

>
> cgf
>

For me, the Ctrl+C thing never works, on cygwin.bat AND xterm.  I would use
Ctrl+Z instead.
So if you hit Ctrl+Z, this would appear (for example):

[1]+   Stopped                           gpg

And then when you type another command, hit enter, and wait the new command
to stop, this would appear:

[1]+   Done                              gpg

Charli
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Cygwin)

iD8DBQFEkdATKGyf4JaPChgRAja/AJsEb3Kj59xIQdYFGVllOc53VUpYdACgpev3
tj5VAIUwbub9Zby6MVqsRbc=
=oxrd
-----END PGP SIGNATURE-----


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/