From: Andrew Cagney <cagney@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] QUIT doesn't seem to be working !?
Date: Fri, 20 Feb 2004 17:51:00 -0000 [thread overview]
Message-ID: <4036490E.9060700@gnu.org> (raw)
In-Reply-To: <20040220170957.GE1713@gnat.com>
>>Yes. I did a quick user poll over lunch and everyone indicated that
>>> contrl-c "works for me" (the sample included heavy java and C++ users!).
>
>
> I am a bit surprised by this, because, as far as I can remember, I
> couldn't understand how this feature could work (no offense meant,
> just to say that it appeared that this functionality was not just
> broken under certain circumstances, but instead was never working).
So was I - a more exact quote of the response was "It's broken!?!?". It
turns out that cntrl-c is being polled sufficiently often for people to
not notice that there is a problem vis:
(gdb) set height 2
(gdb) info frame
Stack level 0, frame at 0x7fffe5c0:
---Type <return> to continue, or q <return> to quit---Quit
> For me, Control-C is working when the debugger is waiting for an event
> from the inferior. However, it is not working when the debugger is
> busy inside a greedy loop (ie the QUIT macro does not abort the
> loop).
Just don't try this at home:
(gdb) while 1
end
(but I suspect that's always been broken as well).
Andrew
next prev parent reply other threads:[~2004-02-20 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 22:22 Joel Brobecker
2003-08-28 14:41 ` Daniel Jacobowitz
2003-11-17 1:00 ` Daniel Jacobowitz
2004-01-19 16:24 ` Daniel Jacobowitz
2004-02-18 20:46 ` Elena Zannoni
2004-02-20 16:14 ` Andrew Cagney
2004-02-20 17:09 ` Joel Brobecker
2004-02-20 17:51 ` Andrew Cagney [this message]
2004-02-26 17:04 ` Daniel Jacobowitz
2004-02-26 17:32 ` Joel Brobecker
2004-02-20 17:06 ` Joel Brobecker
2004-02-23 15:15 ` Elena Zannoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4036490E.9060700@gnu.org \
--to=cagney@gnu.org \
--cc=brobecker@gnat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox