From: Mark Kettenis <kettenis@wins.uva.nl>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] Add FIXME in tracepoint.c:read_actions()
Date: Thu, 23 Aug 2001 13:32:00 -0000 [thread overview]
Message-ID: <200108232032.f7NKWQM03414@delius.kettenis.local> (raw)
I Checked in the attached patch, just in case somebody else stumbles
over it again.
Mark
Index: ChangeLog
from Mark Kettenis <kettenis@gnu.org>
* tracepoint.c (read_actions): Add FIXME for code depending on
STOP_SIGNAL.
Index: tracepoint.c
===================================================================
RCS file: /cvs/src/src/gdb/tracepoint.c,v
retrieving revision 1.25
diff -u -p -r1.25 tracepoint.c
--- tracepoint.c 2001/08/11 00:59:29 1.25
+++ tracepoint.c 2001/08/23 20:29:42
@@ -825,6 +825,11 @@ read_actions (struct tracepoint *t)
/* Control-C quits instantly if typed while in this loop
since it should not wait until the user types a newline. */
immediate_quit++;
+ /* FIXME: kettenis/20010823: Something is wrong here. In this file
+ STOP_SIGNAL is never defined. So this code has been left out, at
+ least for quite a while now. Replacing STOP_SIGNAL with SIGTSTP
+ leads to compilation failures since the variable job_control
+ isn't declared. Leave this alone for now. */
#ifdef STOP_SIGNAL
if (job_control)
{
reply other threads:[~2001-08-23 13:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200108232032.f7NKWQM03414@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--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