Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: eliminate pending_follow.execd_pathname.
Date: Sun, 17 May 2009 16:47:00 -0000	[thread overview]
Message-ID: <200905171747.40189.pedro@codesourcery.com> (raw)
In-Reply-To: <200905171733.40993.pedro@codesourcery.com>

I've applied this follow up patch to clean up comments.

-- 
Pedro Alves

Index: ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.10478
diff -u -p -r1.10478 ChangeLog
--- ChangeLog	17 May 2009 16:31:18 -0000	1.10478
+++ ChangeLog	17 May 2009 16:45:23 -0000
@@ -7,6 +7,8 @@
 	event copy instead.  Release `execd_pathname' once done with
 	handling the event.
 
+	* infrun.c (pending_follow): Remove mention of exec events.
+
 2009-05-17  Hui Zhu  <teawater@gmail.com>
 
 	* i386-tdep.c (i386_process_record): Make it extern.
Index: infrun.c
===================================================================
RCS file: /cvs/src/src/gdb/infrun.c,v
retrieving revision 1.373
diff -u -p -r1.373 infrun.c
--- infrun.c	17 May 2009 16:31:21 -0000	1.373
+++ infrun.c	17 May 2009 16:45:24 -0000
@@ -255,10 +255,9 @@ void init_thread_stepping_state (struct 
 
 void init_infwait_state (void);
 
-/* This is used to remember when a fork, vfork or exec event
-   was caught by a catchpoint, and thus the event is to be
-   followed at the next resume of the inferior, and not
-   immediately. */
+/* This is used to remember when a fork or vfork event was caught by a
+   catchpoint, and thus the event is to be followed at the next resume
+   of the inferior, and not immediately.  */
 static struct
 {
   enum target_waitkind kind;


      reply	other threads:[~2009-05-17 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-17 16:33 Pedro Alves
2009-05-17 16:47 ` Pedro Alves [this message]

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=200905171747.40189.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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