Hi!

while digging into the fact that gdb 6.5 does not close .gdbinit and the 
child programs binary in the child process before execing, I found a typo.
BTW does anyone who is into gdb know how to close the possibly open init 
file without looking at the whole code?

Stephan

index 1bfb98b..a95984d 100644
Binary files a/gdb/.fork-child.c.swp and b/gdb/.fork-child.c.swp differ
index 8940151..44049dc 100644
--- a/gdb/fork-child.c
+++ b/gdb/fork-child.c
@@ -277,7 +277,7 @@ #endif
      (*pre_trace_fun) ();

    /* Create the child process.  Since the child process is going to
-     exec(3) shortlty afterwards, try to reduce the overhead by
+     exec(3) shortly afterwards, try to reduce the overhead by
       calling vfork(2).  However, if PRE_TRACE_FUN is non-null, it's
       likely that this optimization won't work since there's too much
       work to do between the vfork(2) and the exec(3).  This is known

--
Stephan Springl                           BFW Werner Völk GmbH
springl-gdb@bfw-online.de                 Energiemesstechnik & Service
+49 89 82917-452                          Drosselgasse 5
                                           82166 Gräfelfing/München