This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: GDB Ctrl-C Interrupt Fails WORKAROUND

Hash: SHA1

- -----Original Message-----
> From: []On Behalf
> Of Christopher Faylor
> Sent: Thursday, June 15, 2006 3:29 PM
> To:
> 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:


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


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

Version: GnuPG v1.4.3 (Cygwin)


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]