On Sun, Mar 04, 2007 at 07:21:15PM +, Pedro Alves wrote:
>Christopher Faylor wrote:
>
>>? Maybe we're not talking about the same thing but I don't see why it
>>matters what the order of function calls is. If the inferior process
>>has already responded to a CTRL-C you don't want it to get ano
Christopher Faylor wrote:
? Maybe we're not talking about the same thing but I don't see why it
matters what the order of function calls is. If the inferior process
has already responded to a CTRL-C you don't want it to get another
interrupt.
Yep, we were not talking about the same thing
On Thu, Mar 01, 2007 at 01:12:21AM +, Pedro Alves wrote:
>Christopher Faylor escreveu:
>>On Thu, Mar 01, 2007 at 12:15:12AM +, Pedro Alves wrote:
>>>Is there a reason DebugBreakProcess can't be used from inside gdb if
>>>sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid)
>>>
Christopher Faylor escreveu:
On Thu, Mar 01, 2007 at 12:15:12AM +, Pedro Alves wrote:
Is there a reason DebugBreakProcess can't be used from inside
gdb if sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid)
doesn't work?
I suppose that it could be used for that but it might
On Thu, Mar 01, 2007 at 12:15:12AM +, Pedro Alves wrote:
>Is there a reason DebugBreakProcess can't be used from inside
>gdb if sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid)
>doesn't work?
I suppose that it could be used for that but it might be tricky figuring
out when it
Christopher Layne escreveu:
On Thu, Jun 15, 2006 at 11:04:56AM -0400, Christopher Faylor wrote:
I'm happy for you that CTRL-C works for you. It does not work for me.
I'm almost never running gdb from a genuine DOS command prompt.
Sometimes via ssh, sometimes via a terminal emulator. CTRL-C
On Thu, Jun 15, 2006 at 11:04:56AM -0400, Christopher Faylor wrote:
> >I'm happy for you that CTRL-C works for you. It does not work for me.
> >
> >I'm almost never running gdb from a genuine DOS command prompt.
> >Sometimes via ssh, sometimes via a terminal emulator. CTRL-C doesn't
> >work
On Thu, Jun 15, 2006 at 05:28:59PM -0400, Charli Li wrote:
>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
Since using CTRL-Z only works on a runnin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> Of Christopher Faylor
> Sent: Thursday, June 15, 2006 3:29 PM
> To: cygwin@cygwin.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
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 prog
On 15 June 2006 18:39, Kyle McKay wrote:
> On 15 Jun 2006 11:04:56 -0400, Christopher Faylor wrote:
>>> Lacking the ability to interrupt a running program severely limits
>>> gdb's usefulness. Fortunately there's a workaround available.
>>
>> Yep. Use a console window.
>
> Maybe I haven't been
On Thu, Jun 15, 2006 at 10:38:57AM -0700, Kyle McKay wrote:
>On 15 Jun 2006 11:04:56 -0400, Christopher Faylor wrote:
>>>Lacking the ability to interrupt a running program severely limits
>>>gdb's usefulness. Fortunately there's a workaround available.
>>
>>Yep. Use a console window.
>
>Maybe I h
On 15 Jun 2006 11:04:56 -0400, Christopher Faylor wrote:
>Lacking the ability to interrupt a running program severely limits
>gdb's usefulness. Fortunately there's a workaround available.
Yep. Use a console window.
Maybe I haven't been clear. THIS DOES NOT WORK.
Compile the below hellowin.
On Thu, Jun 15, 2006 at 10:43:23AM -0400, Igor Peshansky wrote:
>The workaround would be even better if you didn't need a separate program.
>How about submitting a patch for Cygwin's "kill" (with a new signal,
>SIGDBG or SIGDEBUG)? CGF, would you consider such a patch?
No.
cgf
--
Unsubscribe in
On Thu, Jun 15, 2006 at 01:28:59AM -0700, [EMAIL PROTECTED] wrote:
>On Thu, Jun 15, 2006 at 01:20:40AM -0700, Kyle McKay wrote:
>> I'm almost never running gdb from a genuine DOS command prompt.
>> Sometimes via ssh, sometimes via a terminal emulator. CTRL-C doesn't
>> work in those.
>
>Same
On Thu, Jun 15, 2006 at 01:20:40AM -0700, Kyle McKay wrote:
>On 15 Jun 2006 at 00:44:05 -0400 Christopher Faylor wrote:
>>On Wed, Jun 14, 2006 at 08:29:50PM -0700, Kyle McKay wrote:
>>>If you have ever tried to interrupt a program running under cygwin
>>>gdb, you have probably experienced some frus
On Thu, 15 Jun 2006, Kyle McKay wrote:
> On 15 Jun 2006 at 00:44:05 -0400 Christopher Faylor wrote:
> > On Wed, Jun 14, 2006 at 08:29:50PM -0700, Kyle McKay wrote:
> > > If you have ever tried to interrupt a program running under cygwin
> > > gdb, you have probably experienced some frustration. E
On Thu, Jun 15, 2006 at 01:20:40AM -0700, Kyle McKay wrote:
> I'm almost never running gdb from a genuine DOS command prompt.
> Sometimes via ssh, sometimes via a terminal emulator. CTRL-C doesn't
> work in those.
Same here.
> Finally, it NEVER works no matter what if you are debugging a pr
On 15 Jun 2006 at 00:44:05 -0400 Christopher Faylor wrote:
On Wed, Jun 14, 2006 at 08:29:50PM -0700, Kyle McKay wrote:
>If you have ever tried to interrupt a program running under cygwin
>gdb, you have probably experienced some frustration. Especially if
>the program was built with -mno-cygwin.
On Wed, Jun 14, 2006 at 08:29:50PM -0700, Kyle McKay wrote:
>If you have ever tried to interrupt a program running under cygwin
>gdb, you have probably experienced some frustration. Especially if
>the program was built with -mno-cygwin.
No I never have. In fact I often rely on CTRL-C interru
If you have ever tried to interrupt a program running under cygwin
gdb, you have probably experienced some frustration. Especially if
the program was built with -mno-cygwin.
Here is a workaround.
You've probably discovered that pressing Ctrl-C in the gdb window/
prompt while the program be
22 matches
Mail list logo
