patches/gdb/6.3/820-debian_disable-linux-fork-messages.patch
changeset 96 aa1a9fbd6eb8
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/patches/gdb/6.3/820-debian_disable-linux-fork-messages.patch	Thu May 17 16:22:51 2007 +0000
     1.3 @@ -0,0 +1,46 @@
     1.4 +Status: Proposed upstream after 6.3, not yet committed.
     1.5 +
     1.6 +2004-12-06  Daniel Jacobowitz  <dan@debian.org>
     1.7 +
     1.8 +	* linux-nat.c (child_follow_fork): Call target_terminal_ours before
     1.9 +	printing output.  Use fprintf_unfiltered.  Only print output when
    1.10 +	debugging.
    1.11 +
    1.12 +Index: gdb-6.3/gdb/linux-nat.c
    1.13 +===================================================================
    1.14 +--- gdb-6.3.orig/gdb/linux-nat.c	2004-12-08 18:22:20.386956067 -0500
    1.15 ++++ gdb-6.3/gdb/linux-nat.c	2004-12-08 18:28:49.995585970 -0500
    1.16 +@@ -347,9 +347,13 @@ child_follow_fork (int follow_child)
    1.17 + 	 also, but they'll be reinserted below.  */
    1.18 +       detach_breakpoints (child_pid);
    1.19 + 
    1.20 +-      fprintf_filtered (gdb_stdout,
    1.21 +-			"Detaching after fork from child process %d.\n",
    1.22 +-			child_pid);
    1.23 ++      if (debug_linux_nat)
    1.24 ++	{
    1.25 ++	  target_terminal_ours ();
    1.26 ++	  fprintf_unfiltered (gdb_stdlog,
    1.27 ++			      "Detaching after fork from child process %d.\n",
    1.28 ++			      child_pid);
    1.29 ++	}
    1.30 + 
    1.31 +       ptrace (PTRACE_DETACH, child_pid, 0, 0);
    1.32 + 
    1.33 +@@ -418,9 +422,13 @@ child_follow_fork (int follow_child)
    1.34 +       /* Before detaching from the parent, remove all breakpoints from it. */
    1.35 +       remove_breakpoints ();
    1.36 + 
    1.37 +-      fprintf_filtered (gdb_stdout,
    1.38 +-			"Attaching after fork to child process %d.\n",
    1.39 +-			child_pid);
    1.40 ++      if (debug_linux_nat)
    1.41 ++	{
    1.42 ++	  target_terminal_ours ();
    1.43 ++	  fprintf_unfiltered (gdb_stdlog,
    1.44 ++			      "Attaching after fork to child process %d.\n",
    1.45 ++			      child_pid);
    1.46 ++	}
    1.47 + 
    1.48 +       /* If we're vforking, we may want to hold on to the parent until
    1.49 + 	 the child exits or execs.  At exec time we can remove the old