From: Joel Brobecker <brobecker@gnat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] QUIT doesn't seem to be working !?
Date: Fri, 20 Feb 2004 17:06:00 -0000 [thread overview]
Message-ID: <20040220170605.GD1713@gnat.com> (raw)
In-Reply-To: <16435.52781.747628.886278@localhost.redhat.com>
Hello Elena,
> So, since 6.1 is approaching, I would mark this as a known problem,
> and try to solve it in mainline, after the branch is cut.
Sounds good to me. I will take care of documenting the problem.
Could you take care of fixing it? I remember not being completely sure
of how things were supposed to work when I was looking at this...
Thanks,
--
Joel
> > 2003-08-12 J. Brobecker <brobecker@gnat.com>
> >
> > * event-top.c (handle_sigint): Set quit_flag.
> >
> > Comments? Ok to apply?
> >
> > --
> > Joel
> > Index: event-top.c
> > ===================================================================
> > RCS file: /nile.c/cvs/Dev/gdb/gdb-5.3/gdb/event-top.c,v
> > retrieving revision 1.1
> > diff -u -p -r1.1 event-top.c
> > --- event-top.c 16 Jan 2003 09:46:22 -0000 1.1
> > +++ event-top.c 12 Aug 2003 21:27:57 -0000
> > @@ -967,9 +967,14 @@ handle_sigint (int sig)
> > if (immediate_quit)
> > async_request_quit (0);
> > else
> > - /* If immediate quit is not set, we process SIGINT the next time
> > - through the loop, which is fine. */
> > - mark_async_signal_handler_wrapper (sigint_token);
> > + {
> > + /* If immediate quit is not set, we process SIGINT the next time
> > + through the loop, which is fine. */
> > + mark_async_signal_handler_wrapper (sigint_token);
> > + /* We can also process the signal at certain specific locations
> > + which are explicitely marked by a call to QUIT. */
> > + quit_flag = 1;
> > + }
> > }
> >
> > /* Do the quit. All the checks have been done by the caller. */
next prev parent reply other threads:[~2004-02-20 17:06 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
2004-02-26 17:04 ` Daniel Jacobowitz
2004-02-26 17:32 ` Joel Brobecker
2004-02-20 17:06 ` Joel Brobecker [this message]
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=20040220170605.GD1713@gnat.com \
--to=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